Skip to main content
Glama

CarlNotes

Search a topic's findings

search_topic_findings
Read-only

A CarlNotes topic's findings closest to a query, ranked by meaning over the same index Carl's chat uses. Use it when the user asks Carl or CarlNotes about something on one topic, with phrases like search this topic, or what does Carl have on.

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": {
      "query": "<query>"
    },
    "name": "search_topic_findings"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
cursorNoThe cursor a previous page returned.
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?

readOnlyHint=true already tells the agent this is a safe read, so the description's remaining duty is behavioral nuance. It delivers one valuable trait, results are ranked semantically over the same index as Carl's chat, but says nothing about result counts, pagination via cursor, or what happens when topic_id is omitted or invalid.

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 resource and ranking model, followed by usage triggers. Nothing redundant, though the trailing example phrase 'what does Carl have on' is grammatically awkward and slightly dilutes the trigger list.

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 3-parameter read-only search with no output schema, the description covers what is searched, how results are ranked, and when to reach for it. Gaps around result shape and pagination are modest given the cursor parameter is already documented in the schema.

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 coverage is 67%, and the schema documents cursor and topic_id, so the baseline is a 3. The description implies topic scoping but adds no guidance on the query's phrasing constraints (2000 char max) or on when to supply topic_id versus relying on a topic-bound server.

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 definition states a specific verb and resource: retrieve a CarlNotes topic's findings for a query, ranked by meaning. Scoping to a single topic is explicit ('A CarlNotes topic's findings'), which separates it from a broad search, though it never names the sibling `search` tool that an agent might otherwise pick.

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 an explicit trigger ('Use it when the user asks Carl or CarlNotes about something on one topic') plus concrete sample phrases like 'search this topic' and 'what does Carl have on'. It stops short of telling the agent when not to use it or which sibling handles cross-topic or non-finding lookups.

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.