Skip to main content
Glama

List what is not covered

list_office_procedure_boundaries
Read-onlyIdempotent

List what the office's approved documentation explicitly forbids or says it does not cover. Use it before concluding that something is allowed, or when a question is not covered, to see whether the topic is a documented gap. Returns the boundary statements grouped by document title, or a note that none were found. Takes no question and uses no language model.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_office_procedure_boundaries"
  }
}

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover safety (read-only, idempotent, non-destructive), yet the description adds real value: it discloses the return shape (boundary statements grouped by document title, or a not-found note) and clarifies 'takes no question and uses no language model', distinguishing it from LLM-backed siblings. It does not cover empty-result volume or how boundaries are extracted, keeping it below a 5.

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 short sentences, front-loaded with the purpose, then usage, then return behavior. Every clause carries information; nothing is redundant.

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?

With no output schema and only one optional parameter, the description supplies everything an agent needs: what is returned, its grouping, the empty case, and the fact that no query is required. Nothing material is missing.

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 coverage is 100% and the single optional corpus parameter is fully documented in the schema, including the default behavior and rejection of invented ids. The description adds nothing about the parameter, so the baseline 3 applies.

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 (list) and resource (boundary statements / what documentation forbids or excludes), making the scope unmistakably different from search or ask siblings. The phrase 'explicitly forbids or says it does not cover' pins down exactly which content is returned.

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 two concrete trigger conditions: before concluding something is allowed, and when a question is not covered, to check for a documented gap. It never names the sibling tools or says when not to use it, so it stops short of full routing guidance.

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.