Skip to main content
Glama

Upstream.codes

Read Upstream API

call_api
Read-only

GET any Upstream REST API endpoint as the signed-in user, for anything the other tools don't cover. The OpenAPI document is at /v1/openapi.json (call_api with path /openapi.json). Responses are {data, page?}.

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

Input Schema

NameRequiredDescriptionDefault
pathYesPath under /v1, e.g. /repos/acme/web/labels.
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds real value beyond them by specifying that calls run as the signed-in user and by documenting the {data, page?} response envelope in the absence of an output schema. It still omits error behavior, rate limiting, and what kinds of endpoints are off-limits.

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?

Three short sentences, front-loaded with the capability, then the selection rule, then the discovery endpoint and response shape. Every sentence carries information an agent needs and none is redundant.

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

Completeness4/5

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

For a deliberately open-ended generic GET tool, the description supplies the essentials: scope, auth identity, discovery route, and response envelope. Remaining gaps — pagination mechanics, error semantics, and query-map encoding — are real but secondary for a fallback tool whose contract is intentionally broad.

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 coverage is 50%: `path` is documented in the schema, while `query` (a free-form string map) is not explained anywhere. The description's example of passing /openapi.json as the path reinforces path formatting, but it adds no meaning about how query values should be encoded or combined. Baseline 3 is appropriate since the schema handles half the surface and the description does not compensate for the rest.

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

Purpose5/5

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

States a specific verb and resource ("GET any Upstream REST API endpoint") plus the constraint "as the signed-in user", and explicitly positions itself against the dedicated siblings with "for anything the other tools don't cover". An agent can immediately tell this is the generic escape hatch rather than another targeted reader.

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?

Gives a clear selection rule: use this only for things the other tools don't cover, which effectively routes the agent to the narrower siblings first. The discovery pointer to /v1/openapi.json via the same tool is a genuinely useful procedural hint. It stops short of stating explicit exclusions or when not to reach for it (rate limits, unsupported methods), so it does not reach a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources