Skip to main content
Glama

SinoTechIntel Materials & Tech

Search SinoTechIntel Peer-Reviewed Studies

search_research
Read-only

Search peer-reviewed Chinese scientific research dossiers and empirical intelligence in SinoTechIntel (Advanced Materials, Metallurgy, Semiconductors & Industrial Manufacturing). 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
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 and domain-boundary profile is covered. The description adds genuinely useful behavioral detail by listing what the response contains (titles, original DOIs, abstracts, key takeaways, enrichment version, canonical URLs). It says nothing about result caps, ranking behavior, or what happens on zero hits, which the annotations do not cover either.

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 core action, and the return-value sentence is a compact list rather than prose. The parenthetical subject-area list is slightly bulky but earns its place by defining scope. No filler or repetition.

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?

Five fully documented parameters, a read-only annotation set, and no output schema — the description compensates for the missing output schema by enumerating returned fields. What is missing is decision guidance against the sibling tools, which matters given three plausible adjacent options. Overall adequate to call correctly but not complete on routing.

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%, with page, limit, year, journal, and query all documented including ranges and defaults, so the baseline of 3 applies. The description adds nothing about parameter semantics — no mention of pagination, year filtering, journal filtering, or DOI-prefix search — leaving the schema to do all the work.

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?

Names a specific verb (search) and a well-scoped resource (peer-reviewed Chinese research dossiers in SinoTechIntel, with four named subject areas). It also enumerates the returned fields, so an agent knows exactly what kind of object comes back. It does not, however, distinguish itself from siblings such as get_paper_dossier or extract_empirical_tables, so it stops 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 Guidelines3/5

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

Usage is only implied: the presence of a query/keyword parameter and the phrase 'Search... dossiers' signals discovery-style lookups, but there is no explicit when-to-use statement, no exclusion of the full-text dossier or table-extraction siblings, and no guidance on when a DOI-prefix query is the better entry point. An agent must infer the routing decision itself.

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