Skip to main content
Glama

CarlNotes

Send feedback on a finding

send_finding_feedback

Save the user's own words about why a CarlNotes finding was good or bad for the connected account. Use it when the user explains a rating, with phrases like tell Carl why or give Carl feedback.

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": {
      "finding_id": "<finding_id>",
      "feedback": "<feedback>"
    },
    "name": "send_finding_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
feedbackYes
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 the write profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so safety basics are covered elsewhere. The description adds useful context that the stored content is the user's verbatim words and is scoped to the connected account, but it never says whether repeat submissions append, overwrite, or accumulate — a real gap given non-idempotency. It also omits any permissions or rate-limit context.

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?

Two sentences, front-loaded with the action and followed by the selection guidance, with essentially no filler. The only soft spot is the brand-specific phrasing ('tell Carl why'), which is useful as a matching cue but slightly opaque to a reader unfamiliar with CarlNotes.

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 simple two-parameter write tool with annotations present and no output schema, the description gives enough to select and invoke it, but not quite enough to invoke it correctly in edge cases. It leaves open whether the finding_id must reference an existing finding and what happens on repeated submissions.

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?

With 0% schema description coverage, the description must carry parameter meaning, and it does partially: it makes clear that 'feedback' is the user's own words rather than a summary or score, and that it relates to a specific finding. However, it never describes finding_id's expected format or provenance, nor the 2000-character bound, leaving half the parameter surface undocumented.

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: it saves the user's own words explaining why a CarlNotes finding was good or bad for the connected account. That distinguishes it from rating-type siblings, though it does not name rate_finding or read_finding_rating_note explicitly, so the differentiation is implicit rather than stated.

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 provides concrete trigger conditions — 'when the user explains a rating' and the phrases 'tell Carl why' or 'give Carl feedback' — which is unusually actionable for an agent listening to user intent. It stops short of stating exclusions, e.g. that this is not the tool for casting the rating itself or for reading existing feedback notes.

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.