Skip to main content
Glama
Sign In
cpp-espace-mcp

cpp-espace-mcp

by norm613
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get-work-order

Retrieve work order details by ID; optionally include Costs, Spaces, Tasks, and Attachments.

Instructions

Get details of a specific work order by ID. Use include to get related Costs, Spaces, Tasks, Attachments.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
workOrderIdYesThe work order ID
includeNoComma-separated: Costs, Spaces, Tasks, Attachments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only nature, authentication requirements, rate limits, or error handling. The word 'Get' suggests read-only, but this is not explicitly confirmed, and no other behavioral details are given.

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?

The description is two sentences, front-loads the purpose (Get details of a specific work order), and includes only essential information without unnecessary words.

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?

The tool is simple with 2 parameters and no output schema. The description provides enough context for basic usage (get by ID, include related entities). However, it does not describe the response format or any constraints like pagination, but for a single-object retrieval, this is mostly sufficient.

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%, so the schema already documents both parameters. The description adds no new meaning beyond repeating the include parameter's comma-separated list, which is already in the schema. 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?

The description clearly states the action (Get details) and resource (specific work order by ID), and distinguishes itself from sibling tools like list-work-orders which list multiple. The mention of 'include' for related entities adds specificity.

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

Usage Guidelines3/5

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

The description implies usage for retrieving a single work order, but does not explicitly state when not to use it or compare to alternatives like update-work-order or list-work-orders. The guidance on 'include' is helpful for related data but lacks context on when to use other get-* siblings.

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

Deploy Server

Other Tools