Skip to main content
Glama

What changed on a public endpoint

dialect_changes
Read-onlyIdempotent

Use to see what changed: each reading that changed a field, newest first, with its value, whether it was read sure and when, over the last last_s seconds (default an hour). Side effects: none.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "dialect_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe public endpoint's name, like chamber-a, from dialect_endpoints
limitNo
last_sNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so 'Side effects: none' is largely redundant. The description does add real behavioral detail beyond the annotations: results are ordered newest-first and scoped to a time window defaulting to one hour. However, it omits pagination/limit behavior and the phrase 'whether it was read sure' is unclear enough to be unhelpful.

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 purpose is front-loaded in a single sentence with no filler sentences. The sentence itself is a run-on with awkward constructions ('over the last last_s seconds', 'whether it was read sure') that cost a little readability.

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?

With no output schema, the description carries the burden of describing return values; it does partially specify the shape (per-field change records with value and timing, newest first). But the garbled 'read sure' clause and the undocumented limit parameter leave gaps an agent must guess at.

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 only 33%, so the description needs to compensate. It explains last_s as a seconds-based window defaulting to an hour, which is useful, but says nothing about the limit parameter or its 50-item cap, leaving one of three parameters undocumented in both places.

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 states a specific verb and resource: it returns the change history for a public endpoint, 'each reading that changed a field, newest first.' An agent can distinguish this from a plain current-value read, though it never names a sibling to contrast against.

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?

The opening 'Use to see what changed' gives an implied when-to-use cue, reinforced by the time-window scoping. There is no guidance about when NOT to use it or which sibling (e.g. dialect_read_endpoint for current values) to pick instead, leaving routing to inference.

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