Skip to main content
Glama

rate_call

DestructiveIdempotent

Rate a specific prior metered call - thumbs up or down, plus an optional comment - keyed by the request_id that call's response reported. Works for any metered tool, so you can tell us when a result was wrong, unhelpful, or missed something. Resubmitting the same request_id overwrites your previous rating rather than adding a second one. Auth required; not billed - rating a call you already paid for should not cost more.

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": {
      "request_id": "<request_id>",
      "rating": "<rating>"
    },
    "name": "rate_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
ratingYesThumbs up or down. Resubmitting replaces your earlier rating.
commentNoOptional. What was good or wrong about that call's result.
request_idYesThe request_id from the response of the call you are rating.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / rating / description
      Added value: +"Thumbs up or down. Resubmitting replaces your earlier rating."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare idempotentHint=true, destructiveHint=true, readOnlyHint=false and openWorldHint=false. The description usefully restates the overwrite behavior in plain language and adds two facts the annotations cannot express: auth is required and the call is not billed. It does not say what happens on an invalid/unknown request_id or whether ratings have any retention/review implication, which is the remaining behavioral gap.

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?

Four short sentences, front-loaded with the core action before the scope, overwrite, and billing notes. The closing 'rating a call you already paid for should not cost more' is slightly conversational but does carry real information about billing, so it earns its place. No redundant restatement of the name or title.

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 three-parameter, non-open-world tool with no output schema and annotations covering safety/idempotency, the description covers auth, billing, overwrite semantics, and applicability across all metered tools. Missing error-path information (unknown or already-expired request_id) is the only meaningful hole.

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 coverage is 100%, so every parameter already has a description including the overwrite caveat for rating and the purpose of comment. The description reinforces where request_id comes from ('that call's response reported') but adds no syntax, format, or validation detail beyond the schema. Baseline 3 is appropriate.

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 gives a specific verb and resource ("rate a specific prior metered call") plus the mechanism (thumbs up/down + optional comment) and the key (request_id). It also states the scope ('works for any metered tool'), which is genuinely clarifying. It stops short of distinguishing itself from the sibling send_feedback, so an agent must infer the boundary between the two feedback channels.

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

Usage Guidelines4/5

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

It gives a clear use context — 'tell us when a result was wrong, unhelpful, or missed something' — and a prerequisite ('keyed by the request_id that call's response reported'). What's missing is an explicit exclusion or named alternative, notably versus send_feedback, which is the obvious other feedback tool in the sibling list.

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.