Skip to main content
Glama
LerianStudio

Lerian MCP Server

by LerianStudio

fetcher-execute

Destructive

Execute Fetcher manager API operations such as create, list, validate, or assign by providing the resource, action, and required parameters. Inspect context with fetcher-discover first to ensure accurate requests.

Instructions

Execute Fetcher manager API actions. Use fetcher-discover first to inspect the required organizationId/productName context, path params, query params, and request body shape before calling this tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoRequest body for create/update/validate operations.
actionYesFetcher action to perform (e.g. "create", "list", "validateSchema", "assign").
resourceYesFetcher resource name (e.g. "connections", "connection-migrations", "fetcher-jobs").
pathParamsNoPath parameters as key-value pairs.
productNameNoProduct name sent as X-Product-Name. Required explicitly for some actions like create/assign connection.
queryParamsNoQuery parameters for list/filter operations.
mutationReasonNoHuman-readable audit reason required for mutating live API actions.
organizationIdNoOrganization UUID sent as X-Organization-Id. Required explicitly for scoped actions.
confirmMutationNoRequired as true for POST, PUT, PATCH, or DELETE live API actions.
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the description doesn't need to repeat that. It adds context about requiring confirmMutation and mutationReason for mutating actions, which is useful. However, it doesn't disclose other behavioral traits like rate limits or error handling, and the description doesn't contradict annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, focused sentence that front-loads the purpose and immediately directs to the discover tool. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 9 parameters, nested objects, and no output schema, the description is somewhat thin. It relies heavily on fetcher-discover to fill gaps, which is a reasonable pattern but leaves the agent without direct knowledge of return values or edge cases. The description is adequate but not rich.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters. The description adds minimal extra meaning beyond pointing to fetcher-discover for context. It doesn't explain parameter relationships or provide examples, so it's at baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool executes Fetcher manager API actions, with a specific verb ('Execute') and resource ('Fetcher manager API'). It distinguishes from siblings by referencing fetcher-discover for context, but doesn't explicitly contrast with other execute tools (e.g., midaz-execute).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly instructs to use fetcher-discover first to inspect required context, which is a clear usage guideline. However, it doesn't provide when-not-to-use or alternatives beyond the discover step, so it's not a full 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/LerianStudio/lerian-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server