Skip to main content
Glama

院試hub (Japanese graduate entrance exams)

search_graduate_exam_subjects

大学名・研究科名・科目名(例: 東大 情報理工、京大 数学、電磁気)で院試の科目を探す。収録年度、出題テーマ、年度別解説と解答PDFのURL、公式過去問の配布先、確認済みの入試日程を返す。

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": {
      "query": "<query>"
    },
    "name": "search_graduate_exam_subjects"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes大学・研究科・科目・テーマの語。空白区切りで絞り込む

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations exist, so the description bears the full burden, and while it does enumerate returned fields (収録年度, 出題テーマ, 年度別解説と解答PDFのURL, 公式過去問の配布先, 確認済みの入試日程) it never states that the operation is read-only, whether results are paginated or capped, or what happens when a query matches nothing. Documenting the payload is helpful but does not cover the operational behavior an agent needs with zero annotation coverage.

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?

Two sentences, zero filler, and the search scope is front-loaded before the return-value list. Slightly dense but every clause carries 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?

With no output schema, the description usefully enumerates the returned data, and a one-parameter search tool needs little else. The remaining gap is behavioral (safety profile, result limits, empty-result handling) rather than descriptive.

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 schema already documents the single query parameter, and the description's examples add only marginal meaning about what kinds of tokens are accepted. The whitespace-separated narrowing behavior is spelled out in the schema, not the description.

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 (探す / search) plus resource (院試の科目 / graduate entrance exam subjects) and enumerates the accepted query dimensions with concrete examples (東大 情報理工、京大 数学、電磁気). It does not distinguish itself from siblings like search_exam_themes or find_similar_graduate_exams, so an agent must infer the boundary from names alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied — the description makes clear this is the entry point for finding exam subjects by name — but there is no explicit when-to-use/when-not guidance and no mention of the sibling tools or how the returned 'official past exam distribution sources' overlap with official_past_exam_sources. Nothing is misleading, but routing between siblings is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.