Skip to main content
Glama

space_literature_search

Search primary space and planetary science literature across multiple databases, returning evidence with DOI links and source citations for English or Japanese research queries.

Instructions

宇宙・惑星科学の一次文献(論文・技術報告)を横断検索して根拠を返すツール。

例:「火星の大気流出の研究」「Europa 地下海の証拠」「金星のホスフィン」「はやぶさ2 リュウグウ」

Args: query: 検索語(天体名・現象・ミッション名など)。日本語可。 sources: 検索先。"auto"(既定・日本語クエリなら JAXAリポジトリ・J-STAGE・CiNii+OpenAlex、 英語クエリなら OpenAlex・Crossref・NASA NTRS)/"all"/カンマ区切りで明示。 指定できる名前: openalex, crossref, ads, semanticscholar, wos, ntrs, jaxa_repo, jstage, cinii, zenodo, datacite limit: 返す最大件数(1〜25、既定 10)。 year_from: 出版年の下限(例 2015)。 year_to: 出版年の上限(例 2026)。 sort: "relevance"(既定)/ "citations"(被引用数順)/ "date"(新しい順)。 min_citations: 被引用数の下限。⚠️ 被引用数を持たないソース(NTRS・JAXAリポジトリ・ J-STAGE・CiNii)の文献は除外されます。 open_access_only: OpenAlex でオープンアクセス文献だけに絞る(既定 false)。 include_abstract: 要旨を返すか(既定 true)。長さを抑えたいときは false。 planetary_only: OpenAlex の検索を「惑星科学」概念(concepts.id:C152551177)に限定する (既定 false)。裸の天体名(例「火星」)で関連性を上げたいときに trueにすると、 全文一致で拾われる無関係な高被引用論文(実測: "Mars" で R 言語マニュアル)を排除できます。 銀河・恒星など太陽系外の天体では false のままにしてください。

回答時は DOI リンクと「出典:」行をそのまま提示してください。要旨は要約せず、そのまま引用してください(図の注記と同じく、LLM が書き換えると一次情報と食い違うため)。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "space_literature_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNorelevance
limitNo
queryNo
sourcesNoauto
year_toNo
year_fromNo
min_citationsNo
planetary_onlyNo
include_abstractNo
open_access_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed23 schema fields changedv0.41.4
    • removedInput schema / properties / include_abstract / title
      Removed value: -"Include Abstract"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / min_citations / anyOf
      Removed value: -[
      -  {
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / min_citations / default
      Removed value: -null
    • removedInput schema / properties / min_citations / title
      Removed value: -"Min Citations"
    • addedInput schema / properties / min_citations / type
      Added value: +[
      +  "integer",
      +  "null"
      +]
    • removedInput schema / properties / open_access_only / title
      Removed value: -"Open Access Only"
    • removedInput schema / properties / planetary_only / title
      Removed value: -"Planetary Only"
    • removedInput schema / properties / query / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / query / default
      Removed value: -null
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • addedInput schema / properties / query / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / properties / sort / title
      Removed value: -"Sort"
    • removedInput schema / properties / sources / title
      Removed value: -"Sources"
    • removedInput schema / properties / year_from / anyOf
      Removed value: -[
      -  {
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / year_from / default
      Removed value: -null
    • removedInput schema / properties / year_from / title
      Removed value: -"Year From"
    • addedInput schema / properties / year_from / type
      Added value: +[
      +  "integer",
      +  "null"
      +]
    • removedInput schema / properties / year_to / anyOf
      Removed value: -[
      -  {
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / year_to / default
      Removed value: -null
    • removedInput schema / properties / year_to / title
      Removed value: -"Year To"
    • addedInput schema / properties / year_to / type
      Added value: +[
      +  "integer",
      +  "null"
      +]
    • removedInput schema / title
      Removed value: -"space_literature_searchArguments"
  2. Addedv0.39.0

TDQS

A4.2/5.0
Behavior4/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, and it does disclose non-obvious behavior: min_citations silently drops sources that lack citation counts (NTRS, JAXAリポジトリ, J-STAGE, CiNii), planetary_only restricts OpenAlex to a specific concept ID, and it reports an observed failure mode ('Mars' returning an R manual). It also imposes an output-fidelity rule (keep DOI links and 出典 lines, do not paraphrase abstracts), which is valuable behavioral context an agent would otherwise get wrong. Auth, rate limits, and result field shape are not covered, keeping it at 4.

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?

The purpose line and examples are front-loaded, and each parameter note is short and earns its place. The absolute-length is high for a single tool, but the bulk is genuinely informative rather than redundant, and the final output-fidelity instruction is appropriately separated from the parameter block.

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 ten parameters, zero schema descriptions, and no output schema, the description has to do all the work, and it covers every parameter plus part of the return contract (DOI links, 出典 line, verbatim abstracts). Only the broader result shape — which fields come back beyond abstract and DOI — remains unspecified, which is a minor gap for a search tool.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must define all ten parameters, and it does: it explains the 'auto' source-selection heuristic by query language, enumerates all eleven valid source names, gives the limit range (1–25), acceptable sort values, and year bound examples. It also adds semantics the schema cannot express, such as the citation-count exclusion for min_citations and the concept-ID narrowing behind planetary_only. This fully compensates for the empty schema.

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 states a specific verb and resource ('宇宙・惑星科学の一次文献(論文・技術報告)を横断検索して根拠を返す'), which clearly separates it from the audio, image, video, and dataset-catalog siblings. The worked query examples ('火星の大気流出の研究', 'はやぶさ2 リュウグウ') make the intended input shape concrete. It loses a point only because no sibling is named for explicit contrast.

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?

It gives real conditional guidance: planetary_only=true when the query is a bare body name like 火星, and false for extragalactic objects; include_abstract=false when output length matters; sources='auto' switches source sets by query language. There are no explicit 'do not use this tool when...' exclusions or named alternative tools, so it stops short of a 5.

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