Skip to main content
Glama

Sum a public endpoint's history

dialect_summary
Read-onlyIdempotent

Use for how long or how often over a time: each value's sure seconds, share of the window and how many times it was entered, over the last last_s seconds (default a day). 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_summary"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/non-destructive, and 'Side effects: none' merely restates them. The real value is the disclosure of the return shape — per-value seconds, share of the window, and entry count — which matters because there is no output schema. The behavioral picture is more complete than annotations alone.

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 a single sentence front-loaded with 'Use for', which is good, but the wording is awkward and repetitive ('over the last last_s seconds', 'sure seconds') and includes the redundant 'Side effects: none' that duplicates annotations. Some words do not earn their place.

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 simple two-parameter read tool with no output schema, the description covers purpose, the last_s window semantics, and the returned metrics. It is nearly complete for an agent to call it correctly, with only the garbled phrasing and lack of sibling differentiation holding it back.

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

Parameters4/5

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

Schema coverage is only 50%, with last_s particularly bare (type/default/min/max but no meaning). The description compensates by explaining last_s as the lookback window in seconds and noting the default of one day. The name parameter is well covered by its own schema entry, so the description closes the meaningful gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description conveys that this aggregates an endpoint's history into per-value duration, window share, and entry count, so the resource and metric type are discernible. However, the phrasing ('each value's sure seconds', 'over the last last_s seconds') is garbled and never names the operation as a summary, so it only reaches vague-purpose level. It does not distinguish itself from siblings like dialect_changes or dialect_read_endpoint.

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 for how long or how often over a time' gives an implied when-to-use signal (duration/frequency questions). There is no when-not guidance and no mention of alternatives such as dialect_changes for change history, so the agent must infer conditions on its own.

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