Skip to main content
Glama

Explain an HTTP status code

explain_http_status
Read-onlyIdempotent

Official reason phrase of an HTTP status code, the specification that defines it, and whether a client should retry.

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": {
      "code": "<code>"
    },
    "name": "explain_http_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesHTTP status code, e.g. 429.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. Beyond that, the description adds useful behavioral context by naming the returned information, including the reason phrase, defining specification, and retry recommendation. It does not cover edge cases such as unassigned or unknown status codes, but the annotations lower the disclosure burden.

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?

The description is a single compact sentence fragment with no filler and is front-loaded with the core output. Every part of the phrase 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?

For a simple one-parameter read-only tool, the description is largely complete: it states what information is returned even though there is no output schema. It is slightly incomplete regarding unknown-code handling and usage guidance, but those gaps are minor given the schema and annotations.

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?

The single parameter is fully documented in the schema with type, range, and an example. The description does not add meaning beyond that, so it meets the baseline for high schema coverage rather than enriching parameter semantics.

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 clearly states the tool returns the official reason phrase, defining specification, and retry guidance for an HTTP status code. It is specific about the resource and outputs, but it does not use a direct action verb or explicitly differentiate itself from siblings such as get_request_status.

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 is implied by the description: this is for interpreting a given HTTP status code. However, the description gives no explicit when-to-use guidance, no exclusions, and no comparison with alternatives.

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.