Skip to main content
Glama

院試hub (Japanese graduate entrance exams)

official_past_exam_sources

大学名から、大学公式の院試過去問の配布ページ、公開年度、公式解答の有無を返す。院試hubが1件ずつ確認した記録。

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": {
      "university": "<university>"
    },
    "name": "official_past_exam_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
universityYes大学名(例: 東京大学、阪大)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does add real value: it discloses the three returned attributes and the provenance ('records verified one by one by 院試hub'), which tells the agent the data is curated rather than crawled. It does not say what happens for an unknown university, how coverage varies by institution, or that the call is a non-mutating lookup.

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?

Two short sentences: the first front-loads what is returned and keyed on, the second adds provenance. Nothing is repeated and no sentence is 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 one-parameter lookup with no output schema, the description supplies the essential picture: input key and the three result attributes. The remaining gap is edge-case behavior (no record found, partial coverage), which keeps it shy of a 5.

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?

Only one parameter exists and schema description coverage is 100%, with the schema itself giving the example '東京大学、阪大'. The description restates that the input is a university name but adds no normalization rules, alias handling, or official-vs-abbreviated name guidance.

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?

The description names a specific verb and resource: given a university name it returns the official past-exam distribution page, publication years, and whether official solutions exist. That is concrete enough to separate it from the search-oriented siblings, though it never explicitly says it is a per-university lookup rather than a search.

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 only implied: an agent can infer this is the tool to call when it already has a university name and wants official past-exam sources. There is no explicit when-to-use, when-not-to-use, or routing statement toward search_exam_themes or the other siblings.

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.