Skip to main content
Glama

CarlNotes

Mark a finding consumed

mark_finding_consumed
Idempotent

Mark a CarlNotes finding read for the connected account, the way opening it on the page does. Use it when the user tells Carl or CarlNotes they read a finding, with phrases like mark this read or I read 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": {
      "finding_id": "<finding_id>"
    },
    "name": "mark_finding_consumed"
  }
}

Input Schema

NameRequiredDescriptionDefault
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, and destructiveHint=false, so the mutation and repeat-safety profile is covered. The description adds useful context by equating the effect to opening the item on the page, but says nothing about reversibility, what else changes on the account, or how failure looks.

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, purpose front-loaded before the trigger guidance, with no filler. The slight redundancy between 'mark ... read' and 'mark this read' is harmless but keeps it from being maximally tight.

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 single-parameter mutation with no output schema and adequate annotations, purpose and trigger are covered. The remaining gap is operational: nothing tells the agent where finding_id comes from or what a successful versus no-op call looks like.

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?

One parameter, finding_id, is documented at 0% schema coverage, so the description carries the burden. It implies the target is a single finding but never states the id format or where the agent obtains the id, so the meaning added is only partial.

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 concrete verb and resource ('Mark a CarlNotes finding read') plus the scope ('for the connected account'), and the analogy 'the way opening it on the page does' pins down the exact effect. It does not explicitly differentiate from the sibling bookmark_finding, which also acts on a finding, so it stops short of a 5.

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 an explicit trigger condition ('when the user tells Carl or CarlNotes they read a finding') and concrete example phrasings ('mark this read', 'I read this'), which is strong routing guidance. It offers no exclusions or named alternatives, so an agent must still infer when bookmarking or rating is the better action.

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.