Skip to main content
Glama

Ask the office procedures

ask_office_policies_and_procedures
Read-onlyIdempotent

Answer a question about how this office does something, in plain language, using only the office's own approved procedure documents. Use it when the user asks how their office handles something those documents may cover: a policy, a step, a fee, a deadline, a form, who approves or who to ask. The user does not need to name the documents. Not for questions that have nothing to do with the office's own procedures, such as general knowledge, writing or math. Returns a written answer followed by a Sources list of verbatim quotes that were checked against the documents. If the documents do not cover the question it says so instead of guessing, and rephrasing will not change that. Uses a language model to write the answer.

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": {
      "question": "<question>"
    },
    "name": "ask_office_policies_and_procedures"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
questionYesThe question in plain language, for example: What is our policy on same-day cancellations?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the readOnly/idempotent/closed-world annotations: it discloses that answers are grounded only in approved documents, that output is an answer plus a Sources list of verbatim checked quotes, that uncovered questions produce an explicit refusal rather than a guess, and that rephrasing will not change the refusal. It also discloses the LLM generation step, which matters for trust in the answer.

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?

Front-loaded with the core action, then usage, exclusions, return shape, and fallback behavior in a logical order with no filler. The 'Use it when...' sentence runs long with a colon-list and slows scanning slightly, but nothing is truly expendable.

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?

For a two-parameter question-answering tool with no output schema, the description covers source restriction, output composition, failure behavior, and non-determinism of rephrasing — everything an agent needs to decide to call it and to interpret the result.

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 100%, including the corpus default and rejection of made-up ids, so the baseline is 3. The description's 'the user does not need to name the documents' is largely a prose restatement of what the schema already documents, adding little new meaning about either parameter.

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 — 'Answer a question about how this office does something' — and pins the source of truth to 'only the office's own approved procedure documents.' The stated return shape (written answer plus verbatim Sources list) further separates it from the retrieval-oriented siblings without the agent needing to open a 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 a concrete when-to-use trigger ('the user asks how their office handles something... a policy, a step, a fee, a deadline, a form, who approves') and explicit exclusions (general knowledge, writing, math), plus the reassurance that the user need not name documents. It never names a sibling as the alternative for cases like 'find the exact document text,' so routing versus search_office_policies_and_procedures and verify_office_procedure_quote is left to inference.

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.