Skip to main content
Glama

call_api

Route an HTTP request to a catalog peer API with authentication drawn from the peer's configured environment variables, such as GITHUB_TOKEN or SLACK_BOT_TOKEN.

Instructions

Call a catalog peer HTTP API. Auth comes from the peer's authEnv (GITHUB_TOKEN, SLACK_BOT_TOKEN, CURSOR_API_KEY, ...).

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": {
      "peer": "<peer>",
      "path": "<path>"
    },
    "name": "call_api"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
pathYes
peerYes
httpMethodNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden, and it only discloses the auth mechanism (credentials come from the peer's authEnv, with example variables). It says nothing about whether arbitrary mutating methods are permitted, default httpMethod behavior, rate limits, error/response shape, or any destructive potential of a generic HTTP call — critical gaps for a tool that can issue writes.

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?

Two short sentences with no filler, and the core action is front-loaded ahead of the auth note. The problem is under-specification rather than verbosity, so structure itself is sound.

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?

For a 4-parameter, unannotated, output-schema-less generic HTTP invoker, the description omits method semantics, body handling, error behavior, and response format. The one useful addition — the authEnv credential model — is not enough to make an agent confident about calling it correctly.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, so the description must compensate and largely does not. It clarifies only that `peer` is a catalog peer whose credentials resolve via authEnv; `path`, `httpMethod`, and `body` receive no meaning, format, default, or constraint information.

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?

"Call a catalog peer HTTP API" gives a specific verb (call) and resource (a peer's HTTP API exposed via the catalog), which is meaningfully distinct from a local CLI runner or a single named service. It stops short of explicitly distinguishing itself from siblings such as slack_api that are presumably pre-bound to one peer.

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 or when-not-to-use guidance: nothing says when to pick this over call_cli, slack_api, or route for a given peer, nor any prerequisite such as the peer needing to be listed or probed first. Usage is only inferable from the phrase "catalog peer."

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