Skip to main content
Glama

Rating rule

explain_rating
Read-onlyIdempotent

The 1-5★ rule; with trader, that trader's check per level, radar and stars history. <=1.5 KB.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
catNo
formatNo
traderNoas get_trader

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior4/5

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

Annotations already declare the read-only, idempotent, non-destructive, closed-world profile. Beyond that, the description adds useful behavioral context: a <=1.5 KB response hint and a statement that including a trader changes the returned content to per-level checks, radar, and stars history.

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 description is compact and front-loads the core rule and conditional behavior. It could be clearer, but there is little wasted wording and the size constraint is stated explicitly.

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?

This is a low-complexity tool with no required parameters and rich annotations, so the description does not need exhaustive detail. Still, it leaves two of three parameters unexplained and offers no sibling-routing guidance, which limits completeness.

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

Parameters2/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 must compensate for undocumented parameters. It explains that 'trader' triggers trader-specific results, but it does not clarify what 'cat' filters or what 'format' controls beyond the enum values.

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 identifies the resource as the 1-5★ rating rule and notes that supplying a trader adds trader-specific rating outputs. However, it never states the operation with a clear verb, and phrases such as 'check per level, radar and stars history' are jargon that an agent may not decode confidently.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool instead of get_rating_changes, get_scorecard, or get_trader. The parameter-conditional behavior is implied ('with trader'), but the description does not explain when that mode is appropriate or when another sibling should be selected.

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