Skip to main content
Glama

Search the procedures

search_office_policies_and_procedures
Read-onlyIdempotent

Find the most relevant passages in the office's approved procedure documents for a topic, without a language model. Use it to read the source text, to see what exists on a topic, or when an exact sentence is not found. Returns up to three document titles with an excerpt each, or says no matching procedure was found. Ranking is by keyword overlap, so use the words the documents are likely to use.

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

Input Schema

NameRequiredDescriptionDefault
queryYesKeywords or a short phrase for the topic, for example: late cancellation fee.
corpusNoOptional corpus id. Leave it out to use the office's default corpus, which is right for almost every call; a made-up id is refused.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

With annotations already covering read-only, idempotent, closed-world and non-destructive traits, the description adds real context: no language model is involved, ranking is by keyword overlap, and up to three titles with excerpts are returned with an explicit no-match outcome. With no output schema, that return-shape disclosure is genuinely valuable; only minor gaps remain (excerpt length, ordering of the three results).

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 sentences, front-loaded with what it does, then when to use it, then what comes back and how ranking works. No filler or repetition of the schema.

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

Completeness5/5

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

A low-complexity, two-parameter read tool with no output schema; the description fully covers purpose, return shape, fallback behaviour, and ranking logic while annotations cover the safety profile. Nothing an agent needs in order to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: query terms should be the vocabulary the documents themselves use, and the corpus parameter is framed as default-appropriate and rejecting fabricated ids. That is useful guidance beyond the field definitions.

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 verb and resource ('find the most relevant passages in the office's approved procedure documents') plus a distinguishing mechanism ('without a language model') that separates it from the LLM-backed ask_ sibling. An agent can identify the tool's role without opening the schema.

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?

Gives three concrete use cases (read source text, survey a topic, exact sentence not found) and the last one implicitly routes away from verify_office_procedure_quote. It also advises on query phrasing ('use the words the documents are likely to use'). It never names a sibling explicitly or states a hard exclusion, so it falls short of a 5.

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.