Skip to main content
Glama

Register a risk

register_risk

Register risks against objectives with likelihood, impact, COSO principle mapping, assertions, and fraud flags to structure internal-control reviews.

Instructions

Register a risk to objectives, with likelihood, assertions, related COSO principles and a fraud flag.

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>",
      "description": "<description>"
    },
    "name": "register_risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
causeNo
fraudNo
impactNo
assertionsNo
likelihoodNomedium
principlesNo
descriptionYes
scopeItemIdNo
engagementIdYes

Output Schema

NameRequiredDescriptionDefault
riskYes

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?

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing: no permission/auth requirements, no statement of side effects or whether the risk is deduplicated, and no mention of what registration returns. The field enumeration is parameter content, not behavior.

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 waste; the core action leads and the notable fields follow. It is efficient, though the trailing field list reads more like an inventory than structured guidance.

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?

For a 9-parameter mutation tool with no annotations and a completely undocumented schema, one sentence is insufficient. The existence of an output schema removes the need to explain return values, but the absence of any behavioral or usage context leaves the definition under-specified.

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% across 9 parameters, so the description must compensate. It names likelihood, assertions, COSO principles, and the fraud flag, but leaves the two required parameters (engagementId, description) plus cause, impact, and scopeItemId with no added meaning beyond their bare names.

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?

Names a specific verb and resource (register a risk) and scopes it ('to objectives'), with a list of the notable fields it carries. An agent can tell it creates a risk, but there is no explicit differentiation from its sibling register_control or from list_risks.

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 alternatives such as register_control, nor any prerequisites, ordering, or deduplication guidance. The agent is left to infer usage entirely from the name.

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