Skip to main content
Glama

SinoBioData Biomedical Research

Search SinoBioData Peer-Reviewed Studies

search_research
Read-only

Search peer-reviewed Chinese scientific research dossiers and empirical intelligence in SinoBioData (Biomedicine, Oncology, Clinical Trials & Pharmacology). 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

B3.2/5.0
Behavior3/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 what comes back (titles, DOIs, abstracts, key takeaways, enrichment version V1/V2.1, canonical URLs), but says nothing about ranking, pagination limits beyond the schema, or empty-result behavior.

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, purpose front-loaded, return contents second — no filler. The parenthetical domain list and version tokens are dense but do real scoping work for retrieval.

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 no output schema, the description's return-field enumeration is exactly what the agent needs, and the schema fully documents all five parameters. The remaining gap is behavioral: no statement of result ordering, total-count/pagination behavior, or how V1 vs V2.1 enrichment should affect interpretation.

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%, including the query format example and per-parameter bounds, so the schema carries the parameter burden. The description adds no meaning beyond the schema — it never mentions query syntax, year/journal filtering, or paging semantics.

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) and resource (peer-reviewed Chinese research dossiers in SinoBioData), scoped to named domains and with a return-field summary. It does not name a sibling or explicitly contrast itself with get_paper_dossier or list_topic_hubs, so it falls short of a 5.

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?

No when-to-use, when-not-to-use, or alternative routing is given; the agent must infer that this is the discovery entry point and that get_paper_dossier is for a single known paper. Nothing states whether searches are corpus-bounded in ways the caller should know.

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