cpp-espace-mcp

Overview Schema Source Related Servers Discussions Admin

get-work-order-attachments

Retrieve all file attachments associated with a given work order ID. Access documents, images, and other files linked to maintenance tasks.

Instructions

Get file attachments for a specific work order.

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": {
      "workOrderId": "<workOrderId>"
    },
    "name": "get-work-order-attachments"
  }
}

Input Schema

Name	Required	Description	Default
`workOrderId`	Yes	The work order ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 4, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description provides no behavioral traits beyond fetching attachments. Missing details like return format, permissions needed, or whether attachments are binary files or URLs.

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?

Single sentence that is concise and front-loaded with the core action and resource.

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?

The description is incomplete for a retrieval tool. It does not clarify if multiple attachments are returned, how they are represented, or any pagination behavior. No output schema is provided.

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% with the parameter described as 'The work order ID'. The description repeats this context but adds no new meaning beyond what the schema already provides.

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?

The description clearly states the verb 'Get' and the resource 'file attachments' for a specific work order, distinguishing it from other sibling tools that retrieve different entities.

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 guidance on when to use this tool versus alternatives like get-work-order or list-work-orders. There is no mention of when not to use it or related tools.

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