Skip to main content
Glama

SinoAILab AI & Robotics

Search SinoAILab Peer-Reviewed Studies

search_research
Read-only

Search peer-reviewed Chinese scientific research dossiers and empirical intelligence in SinoAILab (Frontier AI, Robotics, Autonomous Systems & Computing). Returns titles, original DOIs, abstracts, key takeaways, enrichment version (V1/V2.1), and canonical URLs.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default 1)
yearNoOptional publication year filter
limitNoResults per page (default 8, max 15)
queryYesEnglish research keywords, material/drug/crop terms, or DOI prefix (e.g. "solid-state electrolyte", "10.13929/")
journalNoOptional partial journal title filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds real value by disclosing the response payload (titles, original DOIs, abstracts, key takeaways, enrichment version V1/V2.1, canonical URLs), which matters because there is no output schema. It omits ranking/relevance behavior and pagination boundaries, which remain undisclosed beyond the schema constraints.

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, front-loaded with the action and domain, then the return contract. No filler, though the parenthetical topic list and long field enumeration make the second sentence quite dense.

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 five parameters, no nested objects, and no output schema, the description is complete enough to call correctly: scope, inputs implied by schema, and return fields are all covered. Minor gaps are ranking/order of results and page-size behavior, which an agent might want before paginating deeply.

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 page, limit, year, journal, and query are all documented with bounds and examples in the schema itself. The description adds nothing parameter-specific — the mention of DOIs refers to returned values, not to the query parameter's DOI-prefix capability — so the baseline 3 applies.

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 a well-scoped resource (peer-reviewed Chinese research dossiers in SinoAILab, limited to Frontier AI, Robotics, Autonomous Systems & Computing). The enumeration of returned fields further pins down what the tool yields, though it never names a sibling such as get_paper_dossier to differentiate keyword search from dossier retrieval.

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

Usage Guidelines2/5

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

The description gives no when-to-use or when-not-to-use guidance and does not point to an alternative tool. The only implicit signal is the topical scope note, which implies keyword/lookup usage but leaves the agent to infer when keyword search is preferable to fetching a known paper by ID.

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