Skip to main content
Glama

CarlNotes

Bookmark a finding

bookmark_finding
Idempotent

Keep a CarlNotes finding for the connected account so no later brew filters it out, or drop the bookmark. Bookmarking takes the topic's owner or a team that holds it. Use it when the user asks Carl or CarlNotes to keep a finding, with phrases like bookmark this or keep this finding.

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>",
      "is_bookmarked": "<is_bookmarked>"
    },
    "name": "bookmark_finding"
  }
}

Input Schema

NameRequiredDescriptionDefault
finding_idYes
is_bookmarkedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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 mutation safety and repeat-call semantics are covered structurally. The description adds real context the annotations lack: the authorization requirement (topic owner or a holding team) and the effect of the bookmark (surviving later filtering). It still does not spell out which parameter value performs the removal or whether removing a non-existent bookmark errors.

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?

Three sentences, front-loaded with the action, but color words ('CarlNotes', 'no later brew filters it out') cost clarity without adding precision. The permission sentence is useful; the trigger sentences partly repeat each other ('asks Carl or CarlNotes to keep' vs 'bookmark this or keep this finding').

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 two-parameter boolean toggle with no output schema, the essentials are present: purpose, trigger, permission requirement, and reversibility. The remaining gap is mapping the boolean to add-versus-remove and explaining finding_id provenance, which an agent needs before it can fill both required fields confidently.

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 there are two required parameters, so the description must carry the meaning alone. 'Or drop the bookmark' hints at a toggle but never connects that to is_bookmarked=false, and finding_id is never explained (format, where to get it, whether it accepts IDs from read_topic_feed).

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 names a concrete verb and resource: keep (bookmark) a CarlNotes finding on the connected account, and 'or drop the bookmark' signals the toggle-off direction. It is distinguishable from siblings like mark_finding_consumed or rate_finding, though jargon such as 'CarlNotes' and 'so no later brew filters it out' blurs exactly what is being persisted.

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 explicit invocation triggers ('when the user asks Carl or CarlNotes to keep a finding', with example phrases 'bookmark this'/'keep this finding') and a prerequisite ('takes the topic's owner or a team that holds it'). It does not name a sibling alternative or exclusion case, which keeps it short of a 5.

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.