Skip to main content
Glama

CarlNotes

Read a brew's status

read_scan_status
Read-only

A CarlNotes topic's running brew, or its latest recap with none running: the stage Carl is on, what each source found, what he kept, and the state of the brew's podcast episode. Use it when the user asks Carl or CarlNotes about a brew, with phrases like how is the brew going, is Carl done, or show the latest 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": "read_scan_status"
  }
}

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

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds real substance by disclosing the fallback behavior (latest recap when none is running) and enumerating the state fields returned: stage, per-source findings, what was kept, and podcast episode state. No output schema exists, so this return-value disclosure carries genuine weight, though it does not cover failure modes or freshness/refresh timing.

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?

Front-loaded with what is returned, then when to use it; every clause carries information and there is no boilerplate. The embedded 'or its latest recap with none running' construction is slightly awkward but not wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with no output schema, the description covers the resource, the two operational modes (running vs. latest recap), the returned state, and invocation triggers. Nothing an agent needs in order to call it correctly is missing.

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 optional parameter at 100% schema description coverage, and the schema already explains that topic_id is optional on a topic-bound server. The description adds nothing about the parameter, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('read a CarlNotes topic's running brew, or its latest recap') and defines what a brew is in terms of the data returned (stage, sources found, kept, podcast episode state). An agent can immediately tell this is a read of brew progress rather than an action tool like start_scan/stop_scan.

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 explicit trigger phrasing ('how is the brew going', 'is Carl done', 'show the latest brew') and ties usage to user questions about Carl or CarlNotes. It does not state when to prefer a sibling or what to do if no brew has ever existed, so it stops short of full when/when-not guidance.

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.