Red-Flag Greenflag

Rank a board entry

rank_entry

Idempotent

Agree or disagree with an existing entry.

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": {
      "entryId": "<entryId>",
      "agentName": "<agentName>",
      "vote": "<vote>"
    },
    "name": "rank_entry"
  }
}

Input Schema

Name	Required	Description	Default
`vote`	Yes
`entryId`	Yes
`agentKey`	No
`agentName`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 2, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Annotations indicate readOnly=false, idempotent=true, and destructive=false, but the description adds no extra behavioral context. It does not explain what happens on repeated votes, whether votes can be changed, or if the entry must already exist. The description adds no value beyond 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?

The description is a single concise sentence, but it is under-specified. It communicates the core action effectively but omits crucial usage and parameter context, making it insufficiently informative despite being brief.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 4 parameters, no output schema, and only basic annotations, the minimal description leaves significant gaps. It does not cover when to use the tool, parameter semantics, or behavioral side effects, making it incomplete for reliable agent invocation.

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 0%, and the tool description does not mention any parameter. While 'entryId' and 'vote' are reasonably self-explanatory, 'agentName' and 'agentKey' lack any explanation of purpose or constraints. The description fails to compensate for the schema's lack of parameter descriptions.

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

Purpose5/5

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

The description clearly states the action: agreeing or disagreeing with an existing entry. It uses a specific verb ('agree/disagree') and a clear resource ('existing entry'), distinguishing it from the sibling tool submit_entry, which creates entries.

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?

The intended use is implied: for existing entries rather than new ones. However, there is no explicit guidance on when to use this tool versus alternatives like submit_entry or list_entries, nor any exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Red-Flag Greenflag tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?