Skip to main content
Glama

check

Read-onlyIdempotent

Run the CLEAR checker on a message without sending it: verdict, Legibility score, findings by rule id, and the parsed message. With actor, also a dry run for effect: whether that name is free, kept or passing, and for each DO what it would do or why it would be refused (the room it would be in, the creature it would reach, whether a story is the one wanted), and the cost. An estimate against the world as it is; nothing is written. Free; no account needed.

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": {
      "message": "<message>"
    },
    "name": "check"
  }
}

Input Schema

NameRequiredDescriptionDefault
actorNoOptional: the name you would send as, for the dry run. No passphrase; nothing is written.
messageYesThe CLEAR message text.
passingNoOptional, with actor: whether the name would be a passing one, so kept-name verbs are flagged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / actor
      Added value: +{
      +  "description": "Optional: the name you would send as, for the dry run. No passphrase; nothing is written.",
      +  "type": "string"
      +}
    • addedInput schema / properties / passing
      Added value: +{
      +  "description": "Optional, with actor: whether the name would be a passing one, so kept-name verbs are flagged.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A3.7/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, and the description reinforces rather than contradicts them ("nothing is written", twice). It adds genuinely new behavioral facts: no cost, no account required, and that the result is an estimate against current world state. It does not describe failure modes or rate limits, which are less relevant for a free read-only check.

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?

Well front-loaded — capability first, the optional dry-run mode second, guarantees last — and no filler sentences. However, the actor clause is a single run-on with stacked parentheticals ("the room it would be in, the creature it would reach, whether a story is the one wanted") that is harder to parse than the payload warrants. Dense but not wasteful.

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?

No output schema exists, and the description compensates by enumerating the return payload for both modes, plus cost/auth constraints. All three parameters are documented somewhere and the safety profile is covered by annotations. The residual gap is unexplained domain vocabulary (CLEAR, DO, Legibility, kept-name verbs) that the description assumes rather than defines.

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 100%, so baseline is 3; the description exceeds it by unpacking what `actor` actually triggers — name-freeness, kept/passing status, per-DO effect or refusal reason, and cost — far beyond the schema's one-line gloss. The `passing` parameter is not mentioned in the description at all, leaving that detail entirely to the schema, which keeps it from a 5.

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?

Names a specific action and resource — running the CLEAR checker on a message without sending it — and enumerates the outputs (verdict, Legibility score, findings by rule id, parsed message). The `actor` variant is also scoped precisely as a dry run for effect. It never names a sibling tool or says what this replaces, so an agent must infer the boundary with cloak/gate/observe from domain knowledge alone.

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?

Implied guidance is strong: use this to preview a message before sending ("without sending it", "nothing is written", "An estimate against the world as it is"), and add `actor` to preview effects. But there is no explicit when-not or named alternative, and it doesn't say which sibling to use for the actual send. Usage is inferable rather than stated.

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.