Skip to main content
Glama
Sign In
togaf10_EAP_MCP

togaf10_EAP_MCP

by Waganawa-Megumin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Build a cross-mapping matrix

cross_map

Create an empty cross-mapping matrix for capability–value stream, capability–organization, or capability–application; get legend, fill instructions, and how to read filled patterns to spot suspicions.

Instructions

能力 × バリューストリーム / 能力 × 組織 / 能力 × アプリケーションのクロスマッピングについて、空のマトリクス(Markdown 表)、記号の凡例、埋め方、そして「埋めた後に何が見えたら何を疑うか」の読み方を返す。 / For capability × value stream, capability × organisation, or capability × application, return an empty Markdown matrix, the legend, how to fill it, and how to read it once filled — which patterns mean which suspicions.

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": {
      "kind": "<kind>",
      "rows": "<rows>",
      "columns": "<columns>"
    },
    "name": "cross_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesクロスマッピングの種類 / Which cross map
langNo出力言語 / Output languageboth
rowsYes行の項目(通常は能力名)/ Row labels, usually capability names
columnsYes列の項目(段 / 組織単位 / アプリケーション名)/ Column labels: stages, organisational units, or applications

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/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 behavioral disclosure burden. It is transparent that the tool returns an empty template rather than a filled map, and it discloses the auxiliary content (legend, how to fill, how to interpret). No mutation or side effects are implied.

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?

The description is a single compact sentence that front-loads the three use cases before listing output components. The bilingual duplication is justified by the lang parameter, and there is no filler or irrelevant context.

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?

Given there is no output schema, the description adequately covers what the agent will receive: an empty matrix, legend, fill instructions, and reading guidance. It does not explicitly state that rows and columns from the parameters populate the matrix, but the schema already defines those parameters, so the calling contract is sufficiently 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 100%, and the schema already documents the kind enum, rows, columns, and lang parameters. The description adds no additional parameter-level semantics, so the baseline score of 3 applies.

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 names the exact output: an empty Markdown matrix, legend, fill instructions, and reading guidance. It also scopes the tool to three specific cross-mapping kinds, making it clearly distinct from sibling tools like diagram_capability_map or draft_capability_map.

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 description clearly states the usage context: capability × value stream, capability × organisation, or capability × application. It does not explicitly mention exclusions or alternative tools, but the conditions for use are clear enough for an agent to select this tool.

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