Skip to main content
Glama
Sign In

MRR Bench Pricing

by io.github.liuqianyu885
OverviewDiscussionsAdmin

price_changes

Verified list-price changes. Use it to answer 'did X raise its price' with dates and percentages.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
sinceNoOptional YYYY-MM-DD; defaults to last 90 days
domainNoOptional: limit to one tool

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It says the changes are "verified" and mentions dates and percentages, but it does not disclose permissions, ordering, pagination behavior, rate limits, or what happens when no changes are found.

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?

The definition is two short sentences with the resource statement front-loaded and the usage example second. It is efficient, though "Verified" is slightly ambiguous and could use a brief clarification.

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 simple read tool with three optional parameters and no output schema, the description gives the key use case and return dimensions. However, with no annotations and one undocumented parameter, it still leaves gaps around safety, pagination, and parameter behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema documents since and domain but leaves limit without a description, giving 67% coverage. The description adds no parameter meaning at all, so it does not compensate for the undocumented limit behavior or clarify how domain filters results.

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 a specific resource, list-price changes, and frames the use case as answering whether a tool raised its price with dates and percentages. It is clear what the tool returns, though it does not explicitly differentiate itself from siblings such as get_pricing.

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?

It gives a concrete when-to-use scenario: answering "did X raise its price" with dated percentage changes. It does not state when not to use it or name an alternative for current pricing, so the guidance is clear but incomplete.

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

All MRR Bench Pricing toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources