Skip to main content
Glama

Read a public endpoint

dialect_read_endpoint
Read-onlyIdempotent

Use to read a public endpoint now: each field's question, value, whether it was read sure, why not, and since when (Unix seconds) it has held, plus the last 24 hours summed and its latest changes. A value read unsure is what it leaned to. 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_read_endpoint"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so 'Side effects: none' mostly repeats structured data. The real added value is disclosure of the response shape: per-field certainty, the reason a value was unsure, the Unix-second duration a value has held, plus 24-hour aggregates and recent changes — meaningful behavior an agent could not infer from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the usage cue, but the phrasing is convoluted: 'whether it was read sure' and 'A value read unsure is what it leaned to' are cryptic and cost the reader parsing effort. The content earns its place; the wording does not fully.

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?

With no output schema, describing returned fields is essential and the description does so at reasonable depth, while annotations cover safety and idempotency. Gaps are minor: no error/unknown-endpoint behavior and no explanation of what the 24-hour sums aggregate over.

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 coverage is 100% and the single 'name' parameter is already documented with an example ('chamber-a, from dialect_endpoints'). The description adds no additional guidance on the name parameter, 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 ('read a public endpoint') and enumerates what comes back: each field's question, value, read certainty, reason, hold duration in Unix seconds, 24h sums, and latest changes. It is distinguishable from dialect_endpoints (referenced in the schema as the source of valid names) and implicitly from dialect_changes/dialect_summary, though it never names those siblings directly.

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?

'Use to read a public endpoint now' implies a point-in-time snapshot read, which is useful context. However, there is no explicit when-not guidance, no mention of when to prefer dialect_summary, dialect_changes, or dialect_endpoints instead, and no stated prerequisite beyond the schema's pointer to dialect_endpoints.

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