Skip to main content
Glama

Get an engagement

get_engagement

Retrieve a COSO internal-control review engagement by its ID to access scoping, testing, sign-off, and reporting details.

Instructions

Return an engagement by id.

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": {
      "id": "<id>"
    },
    "name": "get_engagement"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Output Schema

NameRequiredDescriptionDefault
foundYes
engagementYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.4/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 behavioral burden, and it says nothing about permissions/auth, what happens when the id does not resolve, or whether the read has side effects. It only implies a safe lookup, without confirming it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

One short, front-loaded sentence with zero waste, which is appropriate for a trivial lookup. The brevity is under-specification rather than disciplined conciseness, since nothing substantive is conveyed.

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 explained, but the definition still omits parameter meaning, error behavior, and any usage context for a tool sitting among 38 siblings. For a read-by-id tool this is minimal but not adequate to route an agent confidently.

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?

Schema description coverage is 0%: the single required 'id' parameter has only a regex pattern and no description. 'By id' weakly signals that the value is an engagement identifier, but adds no format, source, or validity detail beyond the schema's pattern.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Return' plus resource 'an engagement' is clear, and 'by id' hints at single-item retrieval versus the sibling list_engagements. However, the sentence largely restates the name/title ('Get an engagement') and never explicitly distinguishes itself from list_engagements, create_engagement, or get_workpaper-style siblings.

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?

There is no statement of when to use this tool versus list_engagements (to enumerate) or create_engagement (to make one), and no prerequisites or exclusions are given. The agent must infer that 'by id' means a known-identifier lookup.

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