Skip to main content
Glama

List documents in one inquiry

get_matter_documents
Read-onlyIdempotent

Use to show the documents the office uploaded for one inquiry and whether each was read (text ready, needs OCR, read by AI from a scan, rejected). Upload happens in My ESQ CoPilot. For a lawyer or staff member of a law office signed in to ESQ CoPilot for their office. Do not call it for a person looking for a lawyer (use search_attorneys) or for general legal questions.

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": {
      "matter_id": "<matter_id>"
    },
    "name": "get_matter_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
matter_idYesThe inquiry (matter) id from the briefing.

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 declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description goes beyond them by defining the four document read states an agent will encounter and clarifying that this tool only reads while uploads occur in another surface. It does not cover pagination or result limits for a large inquiry, which keeps it short of 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.

Conciseness4/5

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

Purpose and return states are front-loaded in the first sentence, with audience and exclusions following in priority order; three sentences, no filler. The audience sentence is slightly wordy but earns its place by preventing out-of-scope calls.

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

Completeness4/5

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

With no output schema, the description compensates by describing the per-document status values, and it clarifies access scope and that uploads happen elsewhere. For a single-parameter read tool this is close to complete; only volume/pagination behavior is unaddressed.

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 parameter is fully documented with a pattern, so the schema does the heavy lifting. The description adds only 'one inquiry' scoping and the note that the id comes from the briefing, which is marginal beyond the schema. Baseline 3 applies when schema coverage is high.

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 ('show the documents the office uploaded for one inquiry') and enumerates the per-document read states (text ready, needs OCR, read by AI from a scan, rejected), which is exactly what the tool returns. It also names a sibling it is not (search_attorneys), so an agent can distinguish it without opening schemas.

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

Usage Guidelines5/5

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

Gives explicit when-not guidance ('Do not call it for a person looking for a lawyer (use search_attorneys) or for general legal questions') with a named alternative, plus a positive audience condition (lawyer or staff signed in for their office). It also redirects the upload action elsewhere ('Upload happens in My ESQ CoPilot'), preventing a misuse attempt.

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.

Resources