Skip to main content
Glama

upstream_status

Report upstream health, credit spend, and credential state to distinguish missing credentials, rate limiting, and quiet airspace before treating missing data as an outage.

Instructions

Report upstream health, credit spend and credential state.

Use before blaming the data: it separates "no credentials", "rate limited"
and "quiet airspace".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "upstream_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/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 delivers the key behavioral fact: the report separates three distinct failure modes rather than returning a single boolean health flag. The notable gap is that it does not say whether making this status call itself consumes credits, despite prominently reporting "credit spend".

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?

Two short sentences with zero filler: purpose first, then the diagnostic motivation with a memorable tri-state framing. Every clause earns its place.

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?

An output schema exists, so the description need not enumerate return fields, and it still names the three report facets an agent should expect. For a zero-parameter, zero-annotation diagnostic this is close to complete; only the credit-cost question about the call itself is left open.

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?

The tool takes zero parameters, so there is no parameter meaning to convey and the baseline of 4 applies. The description correctly adds nothing spurious about inputs.

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?

"Report upstream health, credit spend and credential state" gives a concrete verb plus three named resources, so the agent knows exactly what this tool returns. It implicitly separates itself from the data-fetching siblings ("use before blaming the data"), but never names an alternative tool, so differentiation is inferred rather than stated.

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?

"Use before blaming the data" is a clear when-to-use trigger: run this diagnostic first when results look empty or wrong. The description also explains what the result discriminates (no credentials vs rate limited vs quiet airspace), which effectively tells the agent what decision this call supports. No explicit when-not-to-use is given, keeping it below a 5.

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