Skip to main content
Glama

CarlNotes

Stop a brew

stop_scan
Idempotent

Stop a CarlNotes topic's running brew. What Carl kept stays, what the brew spent stays charged, and its daily brew comes back. Only the topic's owner or an admin may stop it. Use it when the user asks Carl or CarlNotes to stop, with phrases like stop the brew or cancel this brew.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "stop_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
topic_idNoThe topic's id. Optional on a topic-bound server, which already knows its topic.

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?

The annotations already declare the safety profile (idempotent, non-destructive, not read-only), so the description's real contribution is the consequence statement: retained output stays, already-spent resources stay spent, and the daily slot returns. That is meaningful context beyond annotations. However, the phrasing 'what the brew spent stays charged' and 'its daily brew comes back' is metaphorical and leaves the actual state outcome genuinely unclear, and there is no mention of error behavior when no brew is running.

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, each doing a distinct job: what it does, what happens to state, who may call it, and when to call it. No filler. The jargon slightly reduces informativeness per word, but nothing is wasted.

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 single optional-parameter mutation with no output schema, the description covers effects and permission requirements, which is most of what an agent needs. It does not describe what the call returns or what happens on an already-stopped brew, a minor gap rather than a blocking one.

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 100% and the single topic_id parameter is already documented in the schema as optional on a topic-bound server. The description adds nothing about topic_id, which is acceptable given the schema does the work, so the baseline of 3 applies.

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 plus resource: 'Stop a CarlNotes topic's running brew.' Combined with the title and the sibling start_scan, an agent can tell this halts an in-progress job rather than starting one. The only drag is the idiosyncratic jargon 'brew', which the tool name calls a 'scan', forcing the agent to infer that the two are the same object.

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 supplies concrete trigger phrasing ('stop the brew', 'cancel this brew') and attributes the request to the user, which is genuinely useful for intent matching. What it lacks is an explicit exclusion or named alternative — it never says what to do if nothing is running, or points at start_scan/read_scan_status for other lifecycle actions.

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.