Skip to main content
Glama

Search stored sources

search_sources
Read-only

Search saved source text and retrieve excerpts with version and block locators so you can trace citations back to exact passages in your private library.

Instructions

Search saved source text and return excerpts with version and block locators.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
topic_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description adds the useful detail that results are excerpts carrying version and block locators, but says nothing about pagination, ranking, or what happens when the query matches nothing.

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?

A single front-loaded sentence with the action, the resource, and the return shape, with no filler. Nothing in it is redundant with the title.

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

Completeness3/5

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

The output schema exists, so the description is rightly silent on full return structure, and the annotations cover the read-only profile. However, the three undocumented parameters, especially the nullable topic_id filter, leave an agent guessing about how to constrain a search.

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 description coverage is 0% across three parameters, so the description must carry the load and does not. It never explains query syntax, does not mention that topic_id scopes the search to a topic, and says nothing about what limit controls or its default of 10.

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 states a specific verb ('Search') and resource ('saved source text') and adds what comes back ('excerpts with version and block locators'). That is enough to distinguish it from get_source, which by contrast fetches a single source rather than searching text, though the description never names the alternative.

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?

There is no guidance on when to use this instead of get_source, get_topic_context, or any other sibling, and no stated preconditions. The only implicit cue is the word 'saved', which hints at indexed content rather than live retrieval, but an agent gets no explicit routing rule.

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