Skip to main content
Glama

Add a scope item

add_scope_item

Add a significant account or process to an internal-control review scope by specifying its objective category and assertions, so scoping decisions are documented and testable.

Instructions

Add a significant account/process to the review scope, with its objective category and assertions.

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>",
      "area": "<area>",
      "objectiveCategory": "<objectiveCategory>"
    },
    "name": "add_scope_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaYesSignificant account or process.
inScopeNo
rationaleNo
assertionsNo
engagementIdYes
objectiveCategoryYes

Output Schema

NameRequiredDescriptionDefault
scopeItemYes

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?

No annotations provided, so the description must carry the full behavioral burden. It implies a write operation ('Add') but omits permissions required, idempotency, duplicate handling, side effects, and what happens to existing scope items. This is a significant gap for a mutation tool.

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 wasted words. However, it is overly terse for the complexity of the tool and the low schema coverage.

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?

Given six parameters, three required fields, no annotations, and low schema description coverage, the description is incomplete. Although an output schema exists and need not be explained, the tool lacks usage context, behavioral details, and parameter explanations to be called correctly.

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 only 17%, so the description should compensate. It mentions area (as 'significant account/process'), objective category, and assertions, but ignores engagementId, inScope, and rationale. The provided hints largely restate schema content without adding meaning.

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 and resource: 'Add a significant account/process to the review scope'. The purpose is clear, though it does not distinguish this tool from siblings like create_engagement or register_control beyond the scope-item domain.

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, prerequisites, or exclusions. The description only states what it does, leaving the agent to infer usage context.

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