Skip to main content
Glama

StatuteWire

get_pricing

Read-only

Plans, monthly request quotas, prepaid credit packs and deposit floors, in cents and dollars. No key needed, free, returns no provider data.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuinely new context: it is free, requires no key, and explicitly returns no provider data (a scope/privacy boundary). It does not describe response shape or size, which keeps it short of a 5 for a zero-param read.

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 compact sentences with no filler, and the key qualifiers (free, no key, no provider data) are packed at the end. The opening is a bare noun list rather than a leading statement of purpose, which slightly weakens front-loading.

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 zero-parameter, read-only lookup with no output schema, the description covers what data comes back, its units, and the access requirement. It omits any indication of response structure or whether prices vary by region/tier, but nothing critical to invoking it is missing.

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 no parameters, so the baseline is 4. The phrase 'in cents and dollars' usefully signals the units of the returned monetary values, adding meaning the empty schema cannot convey.

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?

The description enumerates the pricing content (plans, monthly request quotas, prepaid credit packs, deposit floors) so an agent can infer this returns the pricing catalog, but it never states a verb or resource — 'get_pricing' is only restated as a noun list. The subject is identifiable yet the purpose sentence is a fragment, not a clear statement of what the call does.

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 explicit when-to-use guidance, no prerequisites beyond 'No key needed', and no named alternative among the siblings (e.g., how_to_get_access) for access-related questions. The agent must infer that this is the cost/plan lookup tool from the content list alone.

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