Skip to main content
Glama

saagarpatel.dev Portfolio

Search the writing corpus

search
Read-only

Full-text (BM25) search across essays, book chapters, field notes, and pages. Returns ranked matches with a snippet, id, and canonical URL. Pass an id to get_document to read the full text.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 10)
queryYesSearch terms
sectionNoRestrict to one content type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavior: BM25 ranking, the returned fields, and the handoff to get_document. It doesn't mention result-limit or pagination behavior, though the schema's limit cap partially covers that.

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 short sentences, front-loaded with what the tool searches and returns, ending with the follow-up action. Nothing is repeated or wasted.

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?

There is no output schema, so the description must carry the return-value burden, and it does so adequately by naming snippet, id, and canonical URL. Ranking semantics (BM25) are noted, though result ordering thresholds or snippet length aren't described, which is a minor gap for a three-parameter 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?

Schema coverage is 100%, so query, limit, and the section enum are already documented in the schema. The description echoes the content-type scope that the section enum encodes and clarifies that returned ids are inputs to get_document, but adds no syntax or query-format detail. Baseline 3 applies.

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 retrieval mechanism (BM25 full-text search) over a named corpus (essays, book chapters, field notes, pages) and describes the return shape (ranked matches with snippet, id, canonical URL). This clearly separates it from get_document, which reads a single document.

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 description gives an explicit workflow: search first, then pass an id to get_document to read the full text. It doesn't say when to prefer this over list_corpus or other retrieval siblings, so there's no exclusion guidance, but the intended pipeline is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.