Skip to main content
Glama
Sign In

concordance

by com.narrowhighway
OverviewDiscussionsAdmin

study_find

[WORD · internal] The quick-find index — ONE lookup across the whole reference section: archetypes, storyboards, movements, the six study tables, the atlas, harmony, timeline, and the encyclopedia. Each hit is a pointer to the real entry, which carries its own refs and its own honesty. The index finds; it never ranks truth.

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": {
      "q": "<q>"
    },
    "name": "study_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / q / maxLength
      Added value: +4000
  2. Added

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that each hit is a pointer to the real entry rather than the full content, which clarifies the return shape. It omits operational traits like result limits, auth needs, or pagination.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The scope enumeration is front-loaded and informative, but several clauses ('its own honesty,' 'never ranks truth') are atmospheric rather than functional and dilute the signal.

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?

For a search/index tool with no output schema and no annotations, the description communicates scope and the pointer-style result reasonably but leaves out query semantics and result format details that an agent would need.

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% for the single required 'q' parameter. The description never explains what 'q' accepts, how matching works, or any constraints, so it fails to compensate for the schema gap beyond the self-evident single-letter name.

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 and resource (a quick-find index performing ONE lookup across the whole reference section) and enumerates the covered domains. However, the purpose is framed somewhat metaphorically and it never names or contrasts itself against siblings like lookup, search, or locate, so an agent must infer the distinction.

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 explicit when-to-use, when-not-to-use, or alternative routing. The only hint is the poetic 'The index finds; it never ranks truth,' which implies results are unranked but offers no actionable guidance about choosing this tool over search or lookup.

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

All concordance toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources