Skip to main content
Glama

capture

Add a timestamped line to today's Claude/Inbox note for quick thoughts worth keeping that don't need a separate note yet.

Instructions

Add one timestamped line to today's note in Claude/Inbox/, for thoughts worth keeping that do not need a note of their own yet.

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": {
      "content": "<content>"
    },
    "name": "capture"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the behavioral burden, and it does disclose that this is a single-line append into today's note under Claude/Inbox/ and that the timestamp is added for you. It leaves open whether the target note is created if it does not yet exist and whether repeat captures are deduplicated, which are the remaining behavioral unknowns for an append tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the action and destination, with the qualifying use case trailing where it belongs. Every clause earns its place; nothing is repeated or padded.

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 one-parameter append tool with an output schema present (so return values need not be explained) and no nested objects, the description covers action, destination, timestamping, and intended use. The only gap is file-creation behavior when today's note does not exist.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single `content` parameter, so the description must compensate, and it does partially: "one timestamped line" tells the agent the value is a single line of text and that the timestamp is supplied automatically rather than embedded by the caller. It does not specify length limits, formatting, or multi-line handling.

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 effect ("Add one timestamped line") against a specific resource and location ("today's note in Claude/Inbox/"), and the closing clause "thoughts worth keeping that do not need a note of their own yet" carves out a distinct niche from note-writing siblings like write_note. An agent can tell what this does and what it is not for without opening the schema.

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?

The phrase "for thoughts worth keeping that do not need a note of their own yet" gives a clear selection criterion: ephemeral captures rather than full notes. It stops short of naming an explicit alternative (e.g. write_note) or stating when not to use it, so it is strong context rather than full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.