Skip to main content
Glama

CarlNotes

Suggest sources

suggest_sources

Verified sources for a CarlNotes topic name and prompt, each as the option and value create_topic takes. Draws on the account's daily suggestion limit. Use it when the user asks Carl or CarlNotes for sources, with phrases like suggest sources or find sources for this topic.

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": {
      "name": "<name>",
      "prompt": "<prompt>"
    },
    "name": "suggest_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
promptYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag readOnlyHint=false and openWorldHint=true, so the agent knows this is a metered external call; the description earns credit by explaining why, namely that it 'draws on the account's daily suggestion limit.' What is missing is what happens when that limit is exhausted and whether results are cached or deterministic across identical calls.

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 short sentences, front-loaded with the core definition and output contract before the trigger guidance, with no padding. The 'Carl or CarlNotes' phrasing and the phrase examples are slightly redundant but each adds routing value.

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?

With no output schema, the description usefully specifies the return shape (option/value pairs consumable by create_topic) and the quota cost, which is what an agent most needs here. The gap is parameter detail and failure behavior at the daily limit, neither of which is covered anywhere else in the structured data.

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% for two required parameters, so the description carries the full burden and largely does not meet it. It only labels the inputs as a 'topic name' and 'prompt' without clarifying what a prompt should look like, whether it is free-form natural language, or how it relates to the topic name.

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 states a concrete resource and scope: verified sources for a CarlNotes topic name plus prompt, returned in the option/value shape that create_topic consumes. That output contract implicitly separates it from suggest_topics, but no sibling is named outright, so an agent must infer the boundary from the word 'sources' alone.

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 a clear trigger condition ('when the user asks Carl or CarlNotes for sources') plus matching phrases such as 'suggest sources' and 'find sources for this topic', which makes routing easy. It stops short of a 5 because no when-not condition or explicit alternative (e.g., suggest_topics) is stated.

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.