Skip to main content
Glama

Get pricing

get_pricing
Read-onlyIdempotent

Prices for representments.com in US dollars: the free first response, the two monthly plans, and per-case work for a single chargeback over $10,000.

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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds useful content context beyond that: the currency and the exact scope of what is priced, including the $10,000 threshold that qualifies per-case work. It does not say whether the data is static or retrieved live, nor how the prices are presented.

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 sentence with no filler, front-loading the subject (prices for representments.com in USD) before the enumeration. The trailing clause about per-case work over $10,000 is slightly dense but still parses cleanly.

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 no-argument informational tool with annotations covering its safety profile, the description gives enough to know what comes back at a category level. The absence of an output schema means it could have sketched the shape of the response (e.g., plan names and amounts), but it is adequate as written.

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, so the schema carries no semantics to supplement and the baseline of 4 applies. The description correctly implies no inputs are needed by framing the call as a fixed pricing lookup.

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?

The description names the resource precisely: prices for representments.com in US dollars, and enumerates what is priced (free first response, two monthly plans, per-case work above $10,000). That is far more specific than the name alone. It stops short of any explicit contrast with the sibling tools, though the topic gap (pricing vs. disputes/reason codes) makes the distinction obvious.

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 it should call this when a user asks about cost or plans. There is no explicit when-to-use statement, no mention of when not to call it, and no reference to the sibling tools as alternatives for billing-adjacent 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