Skip to main content
Glama

pricing_changes

PAID. Return only the dated Agent Pricing Index corrections at or after a given date — what changed, not the full dataset. Each correction is from a re-read of the vendor's own page. Cheaper than fde equivalent full-dataset calls when you only need to know what moved.

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

Input Schema

NameRequiredDescriptionDefault
sinceNoOptional YYYY-MM-DD. Defaults to 30 days back.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does add real value: the leading "PAID." flags a cost the schema cannot express, and "from a re-read of the vendor's own page" discloses data provenance. However, it says nothing about auth requirements, read-only guarantees, volume of results, or whether the default 30-day window can return nothing, leaving meaningful behavioral gaps.

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?

Three short sentences with the cost flag front-loaded and the scoping constraint before the cost-comparison rationale. No filler, though the phrase "fde equivalent full-dataset calls" is slightly convoluted for what it conveys.

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 one-optional-param read tool with no output schema, the description adequately covers purpose, provenance, cost, and selection rationale. The main omission is any hint of result shape or size for the returned corrections, which matters since 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 100% and the single `since` parameter already documents the YYYY-MM-DD format and the 30-day default. The description only reinforces the inclusive boundary ("at or after"), adding marginal semantics beyond the schema, so the baseline 3 applies.

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 — returns dated Agent Pricing Index corrections at or after a date — and explicitly bounds scope to deltas rather than the full dataset. It gestures at a full-dataset alternative but never names the actual siblings (pricing_rows, fde_catalogue, pricing_benchmark), so an agent must infer which tool it replaces.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

"Cheaper than fde equivalent full-dataset calls when you only need to know what moved" gives a concrete selection condition and names the class of alternative. It stops short of naming the specific sibling tools or stating when not to use this one (e.g., when you need current full pricing rather than changes).

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