Skip to main content
Glama

search_reference

Search and progressively read cold-layer Markdown reference files by query or filename to retrieve relevant facts and context.

Instructions

Progressive reader/search over cold-layer Markdown files in THESEUSMEM_REFERENCE_DIR.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_reference"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
filenameNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It discloses that the tool operates on 'cold-layer Markdown files' in a named directory, which is useful behavioral context, but it does not explain matching semantics, read-only behavior, pagination, or what 'progressive' means.

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?

The single sentence is front-loaded and has no wasted wording. Its brevity is not the problem; the problem is that it omits necessary details.

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

Completeness2/5

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

Because an output schema exists, return values need not be described. However, for a two-parameter search tool with no annotations and 0% schema description coverage, the definition omits usage guidance, parameter semantics, and matching behavior that an agent needs to call it correctly.

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

Parameters2/5

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

Schema coverage is 0%, so the description must compensate. It says nothing about the 'query' or 'filename' parameters, leaving their meaning and interaction undocumented beyond a weak inference from 'search' and 'files'.

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?

The description names a specific action (search/read) and a distinct resource: cold-layer Markdown reference files in THESEUSMEM_REFERENCE_DIR. That distinguishes it from siblings like search_episodes and search_facts, though the phrase 'progressive reader/search' is a bit vague about the actual operation.

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

Usage Guidelines2/5

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

It implies the tool is for searching reference Markdown files, but gives no explicit when-to-use guidance, no conditions for choosing it over search_episodes or search_facts, and no explanation of how query and filename interact.

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