agent-prompt-capture

Overview Schema Source Related Servers Discussions Admin

search_prompts

Search captured prompt text with full-text queries, filter by source or time period, and retrieve results ranked by relevance.

Instructions

Full text search over the captured prompt text, best match first. query is SQLite FTS5 syntax: bare words are AND-ed, "quoted phrases" match exactly, foo OR bar, foo NOT bar and refact* prefixes work. A query FTS5 cannot parse is retried as a literal phrase rather than failing. Remember the text is scrubbed, so searching for an email address or a key will never match. source must be one of: claude_code, codex_cli, opencode, claude_web, claude_code_web, chatgpt_web, codex_cloud. since/until accept an ISO 8601 timestamp ('2026-09-19T14:00:00Z'), a bare date ('2026-09-19'), the word 'now', or a relative duration meaning that long ago: '30m', '24h', '7d', '2w', '3mo', '1y'. Omit until for 'up to now'. limit is capped at 500. Each result carries a bm25 rank (lower = better).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes
`since`	No
`until`	No
`source`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 19, 2026

TDQS

A4.8/5.0

Behavior5/5

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

No annotations are provided, so the description carries the full burden. It discloses query parsing behavior (FTS5 syntax, literal fallback), scrubbing caveat (emails/keys never match), source allowed values, time format options, limit cap of 500, and bm25 rank semantics. Exceptionally transparent.

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?

Long but every sentence adds value. Front-loads purpose, then logically breaks down query syntax, scrubbing note, source, time formats, limit, and rank. Well-structured and necessary; no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for a search tool with complex query syntax. Covers query syntax, parameter constraints, scrubbing caveat, and output rank. Nothing an agent needs to call it correctly is missing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate. It explains every parameter: query syntax, source enum, since/until formats, and limit cap. This adds significant meaning far beyond the schema and fully compensates for the coverage gap.

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 (search) and resource (captured prompt text), and clarifies it is full-text with best-match-first ranking. This clearly distinguishes it from siblings like list_prompts (which lists prompts) and get_prompt (which fetches a specific one).

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?

Provides clear context on when to use: for full-text search with fuzzy matching and specific query syntax. It does not explicitly name alternatives or exclusions, but the purpose is self-evident. Could improve by stating when not to use (e.g., exact ID lookup should use get_prompt).

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

Deploy Server