Skip to main content
Glama

CarlNotes

Rate a finding

rate_finding
Idempotent

Thumb a CarlNotes finding up or down for the connected account, or clear the rating with null. Ratings tell Carl what to keep. Use it when the user rates a finding, with phrases like thumbs up, thumbs down, or more like this.

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": {
      "rating": "<rating>",
      "finding_id": "<finding_id>"
    },
    "name": "rate_finding"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
ratingYes
finding_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, so the mutation/idempotency profile is known. The description adds useful context that the rating is account-scoped, that null clears it, and that ratings affect what Carl keeps. It does not explain permission requirements, whether clearing is possible for any finding, or what the call returns.

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?

Three tight sentences, front-loaded with the core action and the null-clearing option. The motivational line 'Ratings tell Carl what to keep' is mild filler but supports behavior understanding rather than bloating the text.

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?

For a three-parameter mutation tool with no output schema and zero schema description coverage, the definition is adequate but not complete: the unexplained 'note' parameter and the absence of return/error behavior leave an agent guessing in edge cases.

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 0%, so the description must carry the parameter meaning. It usefully documents rating as up/down/null and implies finding_id's role, but the optional 'note' parameter (up to 2000 chars) is never mentioned, leaving a real gap at this coverage level.

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?

States a specific verb and resource (rate a CarlNotes finding), names the scope (for the connected account), and covers the three outcomes: up, down, or clear with null. It is distinguishable from siblings like bookmark_finding or mark_finding_consumed, though it never explicitly contrasts with them.

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?

Gives concrete usage triggers: 'Use it when the user rates a finding, with phrases like thumbs up, thumbs down, or more like this.' That is clear context for selection, but there are no exclusions or pointers to adjacent tools (e.g. read_finding_rating_note) for checking an existing rating.

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.