Skip to main content
Glama
Sign In
togaf10_EAP_MCP

togaf10_EAP_MCP

by Waganawa-Megumin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Archive or unarchive an engagement

archive_engagement

Archive an engagement to hide it from the default list, or restore it anytime with archived=false—no data is deleted.

Instructions

エンゲージメントをアーカイブする(既定の一覧から隠す)。archived=false で元に戻す。データは消えない。 / Archive an engagement so it drops out of the default list, or restore it with archived=false. No data is deleted.

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

Input Schema

NameRequiredDescriptionDefault
langNo出力言語 / Output languageboth
archivedNotrue でアーカイブ、false で解除 / true archives, false restores
engagementIdYes対象の案件 ID(案件名でも可) / Target engagement id (a name also works)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals that archiving is non-destructive, reversible, and only affects visibility in the default list. It does not cover response or error behavior, but that is a minor gap for a simple toggle operation.

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 compact and front-loaded: it states the operation, the effect, the reversal, and the safety property in two short bilingual sentences. Every sentence contributes essential information with no filler.

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?

For a low-complexity boolean toggle with full schema coverage, the description provides enough context to select and invoke the tool correctly. It omits return-value details, but since there is no output schema and the operation is simple, this is an acceptable gap.

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 input schema already documents all parameters. The description reinforces the key behavior of the archived parameter but adds no new parameter semantics beyond what is already present in the schema.

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 states a specific action ('Archive an engagement'), its purpose ('drops out of the default list'), and the reverse operation ('restore it with archived=false'). It also differentiates from delete_engagement by explicitly stating 'No data is deleted.'

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?

It clearly communicates when to use it: to hide an engagement from the default list or to restore it. It does not explicitly name alternatives such as delete_engagement, but the non-deletion caveat gives a clear boundary for when this tool is appropriate.

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