# Sample Inputs and Tools

Use **Sample Inputs** and **Sample Tools** when you want reusable test data and tool definitions inside Fetch Hive. These pages give your team a shared place to store example payloads and JSON tool schemas that can be reused while building and testing.

## Overview

Both pages use the same general pattern: a searchable table with pagination, a **Columns** menu, and dialogs for creating, editing, and deleting entries.

Use **Sample Inputs** for example request bodies, text payloads, or structured inputs you want to keep around for testing. Use **Sample Tools** for reusable tool schemas edited as JSON.

## How do I manage sample inputs? <a href="#manage-sample-inputs" id="manage-sample-inputs"></a>

Open **Tools** in the sidebar, then click **Sample Inputs**.

Use the search field to filter the table by name or description.

Click **Add Sample Input** to create a new saved input.

Enter the name, add an optional description, and paste the sample value you want to store.

Save the input to add it to the table.

To update or remove an entry later, open it from the table and use the edit or delete flow.

## How do I manage sample tools? <a href="#manage-sample-tools" id="manage-sample-tools"></a>

Open **Tools** in the sidebar, then click **Sample Tools**.

Use **Add Sample Tool** to create a new tool schema.

Enter the name and optional description, then define the schema in the JSON editor.

Save the tool when the JSON is valid.

If the JSON is invalid, fix the error in the editor before you save.

To update or remove an existing schema, open it from the table and use the edit or delete flow.

## When should I use each? <a href="#sample-inputs-vs-sample-tools" id="sample-inputs-vs-sample-tools"></a>

Use **Sample Inputs** when you need reusable example data to run through prompts, workflows, or agents.

Use **Sample Tools** when you need reusable JSON tool definitions your team can keep consistent across editor work.

See also: [Integrations](/your-workspace/integrations.md), [Media library](/your-workspace/media-library.md), [Prompts](/prompts/prompts.md), [Workflows](/workflows/workflows.md), and [Agents](/api-reference/agents.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.fetchhive.com/your-workspace/sample-inputs-and-tools.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.