Skip to main content
Glama

CarlNotes

Add an attachment

add_topic_attachment

Add an attachment to a CarlNotes topic you own: the page at a public url, or pasted text with a title, saved as a plain-text file. Carl reads it in the background, and every brew after that scores findings with it. Use it when the user asks Carl or CarlNotes to attach something to a topic, with phrases like attach this page, attach this to the topic, or save this text to the topic.

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": "add_topic_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoA public page to read and attach.
textNoText to attach, with a title, in place of a url.
titleNoThe title of the pasted text.
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.9/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false), the description adds real behavior: the topic must be owned, the fetched page is stored as plain text, Carl reads it in the background, and every subsequent 'brew' scores findings against it. Duplicate/repeat-call behavior is not addressed, which matters given idempotentHint=false.

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 sentences, front-loaded with the capability and followed by effect and trigger phrases; nothing is redundant. The middle clause ('Carl reads it in the background, and every brew after that scores findings with it') is dense but earns its place by explaining a non-obvious side effect.

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 carries the return-side burden and does reasonably: it says what gets stored and what happens next. It does not cover failure modes such as a non-public url or missing ownership, which an agent would benefit from knowing for a write-adjacent tool.

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%, so each parameter is already documented in the schema. The description adds the relationship between url and text ('in place of a url') and reinforces that title belongs to pasted text, but offers no format, length, or failure semantics for the url path. This is the baseline 3 scenario where the schema does the heavy lifting.

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 and resource and enumerates the two accepted inputs: a page at a public url, or pasted text with a title stored as a plain-text file. It also states the ownership precondition ('a topic you own') and the downstream effect on 'brews'. It does not distinguish itself from nearby siblings such as send_to_topic, so it lands just short of a 5.

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?

Usage is stated positively and concretely with trigger phrases ('attach this page', 'attach this to the topic', 'save this text to the topic'), which is strong in-context guidance. There are no explicit exclusions or named alternatives for cases where a different tool (e.g., a post or send tool) would be the right choice.

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.