Skip to main content
Glama

silica_search

Read-onlyIdempotent

Rank passages, functions, and constants by a question's words and vectors before grep or Read. Call for questions with no identifier to locate where behavior is decided.

Instructions

For a question that names no identifier (what a behaviour is, where it is decided, why), call this before any grep (a Grep tool, or grep or rg in a shell), Glob or Read: it ranks passages and, in a source tree, the functions, methods, classes and constants themselves, by the question's words and their vectors. Do not grep for the words of a question; grep for an exact string or a symbol name you already know. Each hit carries its densest width-char window and line; a PDF's section is a page, so on a PDF hit widen width (1200-1500) rather than reading the page. matched_terms are the query terms in the hit; coverage is the share of the query's idf mass they carry (near 1 = every rare term matched, near 0 = only the common words); terms_absent are query terms found nowhere in the corpus. No boolean "no answer" exists: read coverage and matched_terms and decide to stop or rephrase. A hit the dense leg alone found carries dense and coverage 0. In a source tree a hit's section is the symbol, span its lines, and silica_read(path, section=<symbol>) serves its body.

Input Schema

NameRequiredDescriptionDefault
kNoMax hits
queryYesConcise question or description of the concept or behavior to find; preserve known names and identifiers
widthNoCharacters in each hit's window
folderNoOnly documents under this root-relative folder
per_docNoMax sections per document
queriesNoMore query groups, each ranked on its own and fused with `query` by rank: the concept in one, its identifiers in another

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety and repeatability profile is covered. The description goes well beyond that by disclosing output semantics (matched_terms, coverage as idf mass, terms_absent, the dense-only leg with coverage 0), the absence of any boolean 'no answer', the PDF page/section behavior, and the section/span shape of source-tree hits.

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?

Front-loaded with the decisive trigger before any mechanics, and nearly every clause carries unique information (ranking basis, grep exclusion, width/PDF advice, coverage semantics, symbol routing). It is still a long, unbroken block of prose with several parentheticals, which costs it the top mark.

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?

There is no output schema, and the description compensates by naming the return fields and how to interpret them, describing the source-tree and PDF representations, and warning that no 'no answer' signal exists so the agent must read coverage and matched_terms. For a six-parameter search tool this is essentially complete.

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 100%, so the baseline is 3 and the schema already documents all six parameters. The description adds operational meaning for `width` beyond 'Characters in each hit's window' by explaining that the window is the densest `width`-char segment and that on a PDF hit one should widen it to 1200-1500 rather than reading the page, plus the fused-queries intent of ranking concept and identifiers separately.

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 concrete verb and resource (ranks passages, and in a source tree the functions/methods/classes/constants, by the question's words and vectors) and pins the exact scenario that selects it: a question naming no identifier. It explicitly contrasts itself with grep, Glob and Read, so an agent can tell it apart without opening the schema or sibling tools.

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?

Gives explicit when-to-use ('For a question that names no identifier... call this before any grep, Glob or Read') and when-not ('Do not grep for the words of a question; grep for an exact string or a symbol name you already know'). It also routes follow-up work to silica_read for symbol bodies, leaving little to inference.

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