Skip to main content
Glama

get_pool

Retrieve one shared quota pool by ID and return its available units with refills applied, enabling agents to check remaining capacity before drawing.

Instructions

Fetch one pool by id, with its current available units (refill applied).

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": {
      "pool_id": "<pool_id>"
    },
    "name": "get_pool"
  }
}

Input Schema

NameRequiredDescriptionDefault
pool_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full disclosure burden. It does add one genuinely useful behavioral detail — the returned available units already have refill applied, meaning the value is derived rather than raw — but it omits error behavior for an unknown id, permission requirements, and the shape of the response.

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?

A single front-loaded sentence with no filler; the parenthetical about refill is compact and informative. It is nearly ideal, though the fragment structure leaves the return-value framing slightly terse.

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 tool with no annotations and no output schema, the description covers the essentials of what is fetched and that units are refill-adjusted. It is still thin on the response shape, which matters more here precisely because no output schema exists.

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?

Schema description coverage is 0% for the single pool_id parameter, so the description is the only source of meaning. It conveys that pool_id selects exactly one pool, but adds no format, range, or source hints (e.g., where to obtain a valid id) beyond what the schema's integer type already shows.

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 and resource ("Fetch one pool by id") and narrows scope to a single record, which implicitly contrasts with the sibling list_pools. It never names an alternative, so sibling differentiation is only implied 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no mention of list_pools, create_pool, or delete_pool as alternatives. An agent must infer that this is the single-record lookup path purely from the phrase "one pool by id".

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