Skip to main content
Glama

院試hub (Japanese graduate entrance exams)

search_exam_themes

出題テーマ(例: ジョルダン標準形、留数定理、調和振動子)を探し、出題した大学・年度とテーマページの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_exam_themes"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesテーマ名の一部

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the return payload (university, year, theme page URL), which is valuable since there is no output schema. It does not disclose matching semantics (exact vs partial substring, language handling, result limits, or empty-result behavior), which matters for a query tool taking a free-text fragment.

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?

A single well-formed sentence with the action front-loaded, followed by examples and the return shape; no redundant or filler wording.

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, non-destructive lookup tool with no output schema, the description covers what it searches and what it returns. The remaining gap is match behavior and result handling, which is a modest omission rather than a blocking one.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single query parameter is already described as 'part of a theme name', so the baseline is 3. The description goes beyond that by giving concrete example themes, which clarifies the expected granularity of the fragment an agent should pass.

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 and resource (search exam themes) and concretely lists what is returned: universities, years, and theme page URLs. The parenthetical examples (Jordan canonical form, residue theorem, harmonic oscillator) pin down the granularity of a "theme", though it never distinguishes itself from sibling search_graduate_exam_subjects.

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 by the return content (find which university/year used a given theme). There is no explicit when-to-use statement, no exclusion such as 'use search_graduate_exam_subjects to search by subject instead', and no prerequisite or query-narrowing guidance.

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.