Skip to main content
Glama

search_agent_notes

Search notes saved by coding agents like Claude Code and Codex to find project decisions, how-tos, and preferences from earlier sessions, so you can reuse what another agent already learned.

Instructions

Search the notes the user's coding agents (Claude Code and Codex) saved for their own later sessions: project decisions, how-tos, preferences and pointers. Returns matching notes, best first, with their text. Use it to find what another agent or an earlier session already learned. Requires the separate agent-notes permission.

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_agent_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentNoOptional: only this agent's notes.
limitNoMaximum notes (default 8, maximum 30).
queryYesWords to find.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose useful traits: results are ranked best-first and include note text, and a separate agent-notes permission is required (an auth prerequisite the agent would otherwise trip over). It does not explicitly say this is a read-only, non-mutating operation, nor what happens when the permission is missing, leaving notable gaps for an unannotated 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?

Three tight sentences, front-loaded with the resource definition, then return shape, then usage and prerequisite. Nothing is redundant 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 three-parameter search tool with no output schema, the description covers source, return content, ordering, usage motivation, and the permission prerequisite. Only the read-only nature and permission-failure behavior are left implicit.

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 100%, with the agent enum and limit default/maximum already documented in the schema. The description adds only that queries are "words to find," which hints at keyword matching but doesn't clarify matching semantics or how the agent filter interacts with ranking, so it stays at the baseline.

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?

States a specific verb and resource with tight scope: notes saved by the user's coding agents (Claude Code and Codex) for their own later sessions, including the kinds of content (decisions, how-tos, preferences, pointers). This is clearly distinguishable from generic search_files or search_meetings, though it never explicitly contrasts with an alternative tool.

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?

"Use it to find what another agent or an earlier session already learned" gives a clear usage context for when to reach for it. There are no explicit exclusions or named alternatives, so an agent must infer when to prefer other search tools.

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