Skip to main content
Glama

Yamagishi Lab: math-physics papers and separators

search_papers

山岸ラボの数理物理の論文(1〜1127)を、語で探す。題名・副題(分離子の一文を含む)・キーワード・要旨を見る。日本語でも英語でもよい。

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_papers"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldNoどこを探すか(省くと all)
limitNo何本まで(省くと 10)
queryYes探す語(例:4π・立体角・別根・ホログラフィー・Kolmogorov)。空白で区切ると、全部を含むものだけ

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 load. It usefully discloses corpus bounds (1–1127) and precisely which fields are scanned, which is real behavioral context. However, it says nothing about result ordering, what a match returns, whether matching is substring or whole-word, or how the separator field relates to subtitle matching — gaps that matter for a search tool 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the corpus scope, then the searched fields, then the language note. Nothing is padded and no sentence restates the tool name or title.

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 search tool with no output schema and no annotations, the definition covers corpus, fields, and input language adequately. What is missing is any indication of what a result looks like (paper ID, matched field, snippet) and how limit interacts with ranking, which would help the agent interpret output.

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%, so the baseline is 3, and the description earns an extra point by explaining what the ambiguous `separator` enum value means (副題・分離子の一文) — meaning the schema alone does not convey. The multi-term AND behavior lives in the schema rather than the description, but the field descriptions already handle it.

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 gives a specific verb (探す/search) and a specific resource (Yamagishi Lab's math-physics papers, corpus of 1–1127), and enumerates the fields searched (title, subtitle/separator, keywords, abstract). It does not name the sibling tools (get_paper, list_separators) or state how this differs from them, so it falls short of a 5, but an agent can still tell this is a word-based corpus 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: you call it when you want to find papers by a word. There is no explicit when-not guidance, no mention that get_paper should be used to retrieve a known paper, and no note on when to restrict `field` versus searching all. The 'Japanese or English is fine' line does imply acceptable input language, which is useful but not routing 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.

Resources