Skip to main content
Glama

Rating changes

get_rating_changes
Read-onlyIdempotent

/api/v1/changes: list adds, drops and re-rates after a cursor. TSV <=4 KB; json: the API body.

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_rating_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sinceNoa seq or YYYY-MM-DD
actionNo
formatNo
walletsNo0x wallets, slugs or 8-hex
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds genuinely useful behavior beyond that: tsv output is capped at 4 KB while json returns the full API body, which matters for choosing a format. It says nothing about ordering, paging limits, or what "after a cursor" means when since is omitted.

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 clauses, front-loaded with the change types and then the format behavior; nothing is padded. The leading "/api/v1/changes:" route is of limited value to an agent and could be dropped without loss.

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 six-parameter, no-required-args changefeed with no output schema, the description covers the core semantics (what is listed, how since/format behave) but leaves three parameters plus pagination/ordering behavior undocumented. Adequate to call the tool, not enough to call it optimally.

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?

With only 33% schema description coverage, the description partially compensates: "after a cursor" explains the since parameter, and "adds, drops and re-rates" maps onto the action enum values add/drop/rerate. The format semantics (TSV truncation vs raw JSON body) are a real addition over the enum. However, limit, wallets, and category receive no explanation in either schema or description.

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?

"list adds, drops and re-rates after a cursor" gives a specific verb (list) and a clearly scoped resource (rating changes of three kinds), which is far more informative than the title "Rating changes". It distinguishes itself from explain_rating or get_scorecard implicitly by being a changefeed, though no sibling is named.

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 or when-not guidance and no alternatives are named, so an agent must infer from "after a cursor" that this is an incremental polling tool. The cursor phrasing hints at the usage pattern but stops short of stating it.

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