Skip to main content
Glama

grid402_pass_balance

Read-onlyIdempotent

Free Session Pass balance and Spend Controls telemetry (free).

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": {
      "token": "<token>"
    },
    "name": "grid402_pass_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesSession Pass token (pass_g402_...) to inspect.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / token / description
      Added value: +"Session Pass token (pass_g402_...) to inspect."
  2. First observed

TDQS

C2.6/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured fields. The description adds no behavioral context beyond them: it does not say whether an exhausted or expired pass returns an error, what "spend controls telemetry" comprises, or whether the call consumes or meters anything despite being labelled free.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short fragment with no wasted preamble, which is good. However, the parenthetical "(free)" restates nothing useful and the fragmentary noun-phrase form buries the action, leaving the reader to infer that a read occurs.

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 one-parameter, read-only tool whose annotations cover safety and whose only parameter is fully documented in the schema, the essentials are present enough to invoke it. What is missing is any account of the returned telemetry (no output schema exists to cover it) or of failure modes such as an invalid or expired token.

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?

There is a single required parameter and schema coverage is 100%, with the schema itself describing the token as a Session Pass token of the pass_g402_... form. The description adds no further meaning about the token beyond that, so the baseline of 3 applies.

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

Purpose3/5

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

"Free Session Pass balance and Spend Controls telemetry" names a resource and an implied read, so an agent can guess it returns balance and spend-control data for a pass. But there is no verb, no statement of what is actually returned, and the repeated "(free)" marker adds nothing. It also does not distinguish itself from the sibling grid402_pass, which plausibly also concerns passes.

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 guidance at all: no mention of when to call this instead of grid402_pass or grid402_summary, no preconditions on token validity, and no exclusions. The only hint is the parenthetical "(free)", which gestures at cost but not at selection criteria.

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