Skip to main content
Glama

call_api

Invoke provider APIs with stored secrets by name; the broker injects real credentials and returns scrubbed responses.

Instructions

Call a provider API using a stored secret by name. The broker injects the real credential; you only see the (scrubbed) response. Paths are relative to the provider, e.g. secret="stripe-live", method="GET", path="/v1/customers?limit=3". For generic secrets and providers that span many hosts (AWS: upstream="https://s3.eu-west-1.amazonaws.com") pass upstream="https://host".

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

Input Schema

NameRequiredDescriptionDefault
bodyNoJSON object (sent as application/json) or a string sent as-is
pathYespath with optional query, starting with /
methodYes
secretYes
headersNo
upstreamNoonly for generic secrets: https://host[:port]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two important traits: the broker injects the real credential and the caller only sees a scrubbed response. It omits other consequential behavior — that POST/PUT/PATCH/DELETE perform real mutations against a live provider, how provider errors surface, and whether any rate limiting or access policy applies.

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?

Three sentences, front-loaded with the concept before the mechanics, and the inline example packs method/path/secret efficiently. The final upstream sentence is dense and slightly convoluted in its phrasing, but no sentence is filler.

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?

For a six-parameter proxying tool that can mutate live third-party systems with real credentials and has neither annotations nor an output schema, the definition covers the happy path well. It leaves gaps around error/return behavior, access prerequisites hinted at by the request_access sibling, and the destructive potential of non-GET methods.

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

Parameters4/5

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

Schema coverage is 50%, so the description must compensate, and it does for the most important fields: 'secret' is clarified as a stored-secret name with an example ('stripe-live'), 'path' is documented as relative to the provider with a query-string example, and 'upstream' gets an explicit trigger condition and format. 'body' and 'headers' get no added meaning, which keeps this below a 5.

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 opens with a specific verb and resource ('Call a provider API using a stored secret by name') and immediately explains the credential-brokering model. It never names a sibling, so there is no explicit differentiation, but the scope is concrete enough that an agent can distinguish it from list_secrets or explain_policy.

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

Usage Guidelines3/5

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

Usage guidance exists only for the optional 'upstream' parameter (generic secrets and multi-host providers such as AWS), not for the tool as a whole. There is no statement of when to call this versus request_access when a secret is unavailable, or versus list_secrets to discover a secret name, so the when-to-use context is only implied.

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