Skip to main content
Glama

Search command outputs

search_output
Read-onlyIdempotent

Search over recorded terminal commands and their outputs. Find every command that printed a specific message, with context like time, directory, and exit code.

Instructions

Full-text search over recorded terminal commands AND their outputs — finds e.g. every command that ever printed 'connection refused'. Returns plain text, one block per match: id, time, cwd, exit code, the command line, and a snippet around the match (secrets are masked by default). Use this to FIND which command said something; use list_commands to browse recent history without a search term, and get_output to read a full output once you have an id. No matches returns an empty result, not an error. Read-only: never re-runs anything.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoonly commands run in this directory or beneath it (absolute path, or '.' for the server's cwd)
exitNoonly this exit code (a number), or 'fail' for any nonzero
hostNoonly commands from this synced machine ('local' = this machine)
limitNomax results (default 20, max 100)
queryYestext to search for in command lines and outputs (substring match; case-insensitive)
sinceNoonly commands newer than this: 30m, 2h, 3d, 1w, or 2006-01-02[ 15:04]
Behavior5/5

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

Descriptions adds context beyond annotations: notes read-only nature, secrets masked by default, return format includes id, time, cwd, exit code, command line, and snippet. Annotations already declare readOnlyHint, idempotentHint, destructiveHint; description enriches with specifics.

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?

Every sentence serves a purpose; the description is concise yet informative. It is well-structured, front-loaded with the main function, and uses clear examples.

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?

Given no output schema, the description fully covers the return format and key behaviors (secrets masked, read-only, empty results behavior). All 6 parameters are covered in the schema, and the description adds important context for a search 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?

Since schema description coverage is 100%, baseline is 3. The description does not add additional parameter details beyond what is in the schema.

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?

The description clearly states the tool performs full-text search over recorded terminal commands and outputs, with a concrete example. It specifies the verb 'search' and resource 'command outputs' precisely.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit guidance is provided: use this to find which command said something, with sibling tool alternatives listed (list_commands for browsing without search, get_output for full output after finding an id). Also explains behavior for no matches.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/soren-achebe/backscroll'

If you have feedback or need assistance with the MCP directory API, please join our Discord server