Skip to main content
Glama

list_spending_mandates

Read-onlyIdempotent

Controller lists its spending mandates and gross authorization usage. Never returns token hashes or tokens.

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": "list_spending_mandates"
  }
}

Input Schema

NameRequiredDescriptionDefault
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds one useful disclosure beyond that: token hashes/tokens are never returned. It says nothing about pagination, ordering, or result size for a list operation, so the addition is modest.

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?

Two short sentences, front-loaded with the scope and ending with the security constraint. 'Token hashes or tokens' is slightly redundant but otherwise there is no wasted wording.

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 simple read-only list tool with rich annotations and no output schema, the core purpose is covered. Missing are pagination semantics for offset and a definition of the returned 'gross authorization usage', which an agent would need to page and interpret results.

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

Parameters2/5

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

Schema coverage is 0% and the description never mentions the sole parameter, offset, nor the 0-10000 bound or any page size. The meaning of 'gross authorization usage' is also left undefined, so the description does not compensate for the undocumented schema.

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?

Specific verb ('lists') plus resource ('spending mandates') and an extra stated output ('gross authorization usage'), which separates it from mutation siblings like create_spending_mandate or revoke_spending_mandate. It does not explicitly say how it differs from current_spending_mandate, so it stops short of a 5.

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?

No statement of when to call this versus current_spending_mandate or the other mandate tools, and no prerequisites or exclusions. Usage is only inferable from the word 'lists'.

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