Skip to main content
Glama
MCP Server Boilerplate

MCP Server Boilerplate

by jeandbonicel

Fetch API

fetch-api

Send HTTP GET, POST, PUT, or DELETE requests to external APIs and return responses, including optional headers and request bodies for integrations and data retrieval.

Instructions

Makes HTTP requests to external APIs and returns the response.

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": {
      "url": "<url>"
    },
    "name": "fetch-api"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL to fetch
bodyNoOptional request body (for POST/PUT)
methodNoHTTP methodGET
headersNoOptional HTTP headers

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the external-network and non-read-only nature is covered. The description adds only that a response is returned, with no disclosure of error behavior, timeouts, rate limits, credential requirements, or that methods like DELETE are irreversible side effects.

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

Conciseness4/5

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

One compact sentence with the verb and outcome front-loaded and no filler. It is well sized, though the brevity comes at the cost of the behavioral detail a generic HTTP tool needs.

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?

There is no output schema, and 'returns the response' gives no indication of response shape, status-code handling, or error format for an open-world tool. Combined with an unannotated mutation surface (POST/PUT/DELETE) and no auth or failure-mode context, an agent lacks what it needs to call this safely and interpret results.

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 all four parameters (url, method, headers, body) already carry descriptions and an enum for method. The description adds no extra meaning about how method interacts with body or which headers matter, so the baseline 3 applies.

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?

States a concrete verb and resource ('Makes HTTP requests to external APIs') with the effect ('returns the response'), so an agent understands the operation immediately. It does not differentiate from siblings (calculator, database, file-ops) or clarify whether it is generic passthrough versus a specific integration.

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?

There is no when-to-use guidance, no prerequisites (auth, allowed hosts, credentials), and no exclusions or alternatives. The agent must infer entirely on its own when this is preferable to the sibling 'database' or 'file-ops' tools.

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