Skip to main content
Glama

search_sources

Search pinned manuals and scenario descriptions by exact muscle or joint ID to retrieve source, hash, and license data; never computes anatomy.

Instructions

Offline FTS5 search of pinned manual, exact muscle/joint IDs and scenario descriptions; source/hash/license, never computed anatomy.

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

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.1

TDQS

B3.2/5.0
Behavior2/5

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

With zero annotations, the description carries the full behavioral burden. It usefully discloses that the search is offline, keyword-based (FTS5, not semantic), scoped to version-pinned content, and returns provenance fields (source/hash/license). However it says nothing about ranking, what limit does, error behavior on malformed FTS5 queries, or whether results are ranked or filtered, which are material for a search tool.

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?

A single dense sentence with no filler, front-loaded with the core operation. The heavy use of semicolons and slashes packs a lot into one line but edges toward being hard to parse.

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?

An output schema exists, so return structure needn't be explained, and the description does note provenance fields anyway. But for a two-parameter search tool with no annotations, missing query-syntax and limit/ranking guidance leaves real gaps an agent would need to close by trial and error.

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 description coverage is 0%, so the description should compensate. It partly does by enumerating what the query can target ('exact muscle/joint IDs', 'scenario descriptions', manual text) and hinting that ID lookups are exact rather than fuzzy. It says nothing about query syntax/operators or the meaning of 'limit' (default 5, ranking implications).

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?

States a specific verb+resource: an offline FTS5 full-text search over a pinned manual, exact muscle/joint IDs, and scenario descriptions. The trailing phrase 'never computed anatomy' implicitly separates it from lookup tools like get_joint_info, though the telegraphic phrasing ('pinned manual', 'source/hash/license') is cryptic at first read.

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

Usage Guidelines3/5

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

There is no explicit 'use this when...' guidance, but 'never computed anatomy' functions as an exclusion that signals this is for citing documented source material rather than fetching computed values. The agent must infer that alternative from context rather than being routed to a named sibling.

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