Skip to main content
Glama
Sign In
mcp-blanko

mcp-blanko

by StenSeegel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

fetch_data

Make HTTP requests to an external API by specifying an endpoint path and an optional HTTP method. Retrieve data from any API endpoint.

Instructions

Placeholder for a tool that calls an external API. Replace the handler with your own API logic.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "endpoint": "<endpoint>"
    },
    "name": "fetch_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodNoHTTP methodGET
endpointYesAPI endpoint path (e.g., /users/123)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/5.0
Behavior2/5

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

No annotations exist, so description must disclose behavioral traits. It only says 'calls an external API' without detailing side effects, authentication, rate limits, or error behavior, providing minimal transparency.

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

Conciseness3/5

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

Single sentence is concise but lacks substantive information. As a placeholder, it is appropriately short but not optimally structured for usability.

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

Completeness2/5

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

With 2 parameters and no output schema, the description fails to explain return format, expected behavior, or error cases. Incomplete for a tool intended to call an external API.

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?

Input schema coverage is 100% with clear descriptions for both parameters (method enum and endpoint string). The description adds no extra meaning, so baseline score of 3 is appropriate.

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

Purpose2/5

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

The description states it calls an external API but is vague and labeled as a placeholder. It does not distinguish what data or endpoint, making it unclear for an AI agent to select specific purpose vs siblings like hello_world or process_order.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives. No exclusions or comparisons provided, leaving the agent without context for appropriate selection.

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

Deploy Server

Other Tools