Skip to main content
Glama

Create an engagement

create_engagement

Creates a new internal-control review engagement and returns the engagement id required by all later COSO review tools.

Instructions

Create a new internal-control review engagement. Returns the engagement id used by all later tools.

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": {
      "title": "<title>",
      "entity": "<entity>"
    },
    "name": "create_engagement"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoOptional explicit engagement id.
titleYesEngagement title.
entityYesEntity or business unit under review.
periodNoReview period, e.g. 2025 or 2025-H2.
materialityNo

Output Schema

NameRequiredDescriptionDefault
engagementYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that the tool creates persistent state and returns an id required by later tools, which is useful beyond a simple return format, but it omits permissions, idempotency, and side effects.

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?

Two tight sentences with no waste, front-loading the purpose and then the key return dependency. Every sentence earns its place.

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

Completeness3/5

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

The output schema means return values need not be explained, and the schema covers most parameters. However, as a mutation tool with no annotations, the description should say more about permissions or behavioral constraints to be fully complete.

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 80%, so the schema already documents parameters well. The description adds no syntax or role details for title, entity, period, or materiality, matching the baseline for high coverage.

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 (Create) and resource (internal-control review engagement), making clear what the tool does. It does not explicitly compare to siblings like get_engagement or list_engagements, but the verb alone distinguishes it.

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

Usage Guidelines4/5

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

The sentence 'Returns the engagement id used by all later tools' gives clear context that this is the entry point for downstream operations. No exclusions or alternative tools are named, but the foundational role is evident.

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