Skip to main content
Glama

List workpapers

list_workpapers

Lists the workpapers assembled for a COSO internal-control engagement, enabling reviewers to inspect available evidence and review materials.

Instructions

List the workpapers assembled for an engagement.

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": {
      "engagementId": "<engagementId>"
    },
    "name": "list_workpapers"
  }
}

Input Schema

NameRequiredDescriptionDefault
engagementIdYes

Output Schema

NameRequiredDescriptionDefault
countYes
workpapersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it delivers almost none. 'List' implies a safe read, but there is no statement about pagination, ordering, result limits, or whether workpapers from other engagements are excluded.

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?

A single front-loaded sentence with no filler, which is appropriate sizing for a simple list tool. It is efficient, though it may be too terse given the gaps elsewhere.

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

Completeness2/5

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

An output schema exists so return values need not be described, but the definition still omits pagination behavior, ordering, the meaning of the engagementId, and any read-only/safety signal in the absence of annotations. For a tool in a 40-tool suite it does too little to be self-sufficient.

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?

The single parameter engagementId has 0% schema description coverage, and the description only gestures at it with 'for an engagement' – no format, ID source, or constraint is explained. With one undocumented parameter, the description does not compensate for the coverage gap.

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 (list) and resource (workpapers) with a clear scope (assembled for an engagement). It is distinguishable from get_workpaper (single retrieval) and assemble_workpaper (creation) by the plural/listing form, though it never names those siblings explicitly.

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?

No when-to-use or when-not-to-use guidance. The agent is left to infer that this is the bulk-listing counterpart to get_workpaper and that an engagementId is required; nothing routes it between the ~40 sibling tools.

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