Skip to main content
Glama

Chessar.io

highlights

Read-only

Notable moments on the board, newest first: big mates, raids, comebacks, long survivals, first mates, recruit streaks. Needs no API key.

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": {
      "world": "<world>"
    },
    "name": "highlights"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1..50, default 20
worldYesWorld id, see the worlds tool (e.g. 10s)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description usefully adds the return ordering ('newest first') and an auth note ('needs no API key') that an agent could not get from structured fields. It doesn't discuss pagination or what happens when fewer moments exist than the limit, but the additions are meaningful beyond the annotation.

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

Conciseness5/5

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

Two sentences, front-loaded with the resource and ordering, followed by the category list that defines 'notable'. No filler or redundancy.

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 2-parameter read-only list tool with no output schema, the description covers what is returned, the ordering, and the auth posture. The only notable omission is saying the results are scoped to the requested world, which the agent must infer from the required parameter.

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 100%, with the world enum documented inline and limit described as '1..50, default 20', so the baseline is 3. The description adds no further meaning about how 'world' or 'limit' shape results — notably it doesn't hint that highlights are per-world.

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 concrete resource ('notable moments on the board') and enumerates the event categories it returns (big mates, raids, comebacks, long survivals, first mates, recruit streaks), so an agent knows exactly what data this yields. It also states ordering ('newest first'). It stops short of a crisp verb like 'list' and doesn't explicitly differentiate itself from siblings such as leaderboard or moves, but the content scope is unmistakable.

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?

Usage is implied rather than stated: an agent can infer this is the tool for surfacing notable gameplay moments, but there is no explicit when-to-use, no exclusion, and no pointer to an alternative sibling for related queries. The 'needs no API key' note is about access, not selection.

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