Skip to main content
Glama
Sign In
togaf10_EAP_MCP

togaf10_EAP_MCP

by Waganawa-Megumin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Find the primary source for a topic

check_official_source

Return primary source URLs for a topic and list what this server lacks. Use it when you doubt an answer, suspect a newer edition, or need authoritative wording; your client fetches the sources.

Instructions

話題を渡すと一次情報の URL と「このサーバーが持っていない範囲」を返す。答えが疑わしいとき・版が古い疑いがあるとき・原文が必要なときに使う。サーバーは取得しない。読むのはクライアント側。 / Return the primary source URLs for a topic, plus what this server deliberately lacks. Use it when you doubt an answer here, suspect a newer edition, or need authoritative wording. This server does not fetch; your client does.

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": {
      "topic": "<topic>"
    },
    "name": "check_official_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo出力言語 / Output languageboth
topicYes調べたい話題。例 "ADM フェーズ B の成果物" / The topic to look up

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?

With no annotations, the description carries the full burden, and it discloses a critical behavioral trait: 'This server does not fetch; your client does.' It also reveals the tool's scope limitation ('what this server deliberately lacks'). This adds meaningful context beyond the schema. Minor gaps remain around output format or whether any network call happens, but the key non-fetching behavior is clearly stated.

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: first the purpose, then the use cases, then the critical server-vs-client caveat. The bilingual duplication is purposeful for the audience and not wasteful. Every sentence contributes distinct information.

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 simple referral tool with no output schema, the description covers purpose, usage triggers, and the key server behavior. It does not detail the exact return structure, but the statement 'primary source URLs plus what this server lacks' gives a sufficient mental model. The absence of annotations is partially offset by the explicit server-behavior note.

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 both parameters (lang, topic) are already well-described in the schema with examples and enums. The description does not add extra parameter-level detail, which is acceptable given the schema's completeness. Baseline 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 states a specific verb ('Return') and a precise resource ('primary source URLs for a topic, plus what this server deliberately lacks'). It clearly distinguishes this tool from siblings like search_togaf or reference by emphasizing that it returns authoritative sources rather than fetched content. The bilingual phrasing reinforces the same meaning without ambiguity.

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 gives explicit trigger conditions: 'when you doubt an answer here, suspect a newer edition, or need authoritative wording.' This is clear context for when to use the tool. However, it does not name alternatives or state when not to use it, so it stops short of the highest bar.

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