Skip to main content
Glama

Read your Poacher account

read_account
Read-onlyIdempotent

Read prepaid balances, the monthly cap, time zone and billing environment. Money is in USD micros (1,000,000 micros = 1 USD). Changes nothing.

Permission: account:read.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so 'Changes nothing' adds little. What the description does add is genuinely valuable: the money unit conversion rule (1,000,000 micros = 1 USD) and the required 'account:read' permission scope, both of which prevent misinterpretation and auth failures.

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 plus a separate permission line, with the returned fields front-loaded and the unit caveat immediately after. No filler, no restatement of the title, and the auth requirement is visually separated so it is easy to scan.

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

Completeness5/5

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

An output schema exists, so return values need not be spelled out, yet the description still supplies the one thing the schema cannot convey: that monetary values are in micros. Combined with the permission scope and the no-side-effects note, an agent has everything needed to call this correctly.

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, which is the baseline-4 case; there is nothing for the description to disambiguate at the input level. The schema is empty and fully described, so no compensating text is needed.

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?

States a specific verb (read) and resource (account) and enumerates exactly what is returned: prepaid balances, monthly cap, time zone, billing environment. That is far beyond restating the name. It does not explicitly distinguish itself from nearby tools like get_capabilities, so it falls 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is the tool for account/billing state because the returned fields are named. There is no explicit when-to-use statement, no when-not-to-use, and no pointer to an alternative such as get_capabilities for capability questions.

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