Skip to main content
Glama

SinoGreenTech Clean Energy

Search SinoGreenTech Peer-Reviewed Studies

search_research
Read-only

Search peer-reviewed Chinese scientific research dossiers and empirical intelligence in SinoGreenTech (Clean Energy, EV Batteries, Energy Storage & Grid Engineering). 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.7/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 safety is covered; the description adds real value by enumerating the returned fields (titles, original DOIs, abstracts, key takeaways, enrichment version V1/V2.1, canonical URLs) in the absence of an output schema. It does not disclose coverage limits, pagination ceilings, or what happens on zero results, but the return-surface disclosure is substantive beyond the annotations.

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 verb and domain scope, with the second sentence dedicated to return contents. Dense but nearly all of it earns its place; only the phrase 'empirical intelligence' is soft marketing filler.

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 responsibly covers return values, and all five parameters are fully documented in schema. What is missing is agent-facing routing guidance relative to sibling retrieval tools, which leaves a small but real gap for a 5-parameter search entry point.

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% (all five parameters, including query keyword/DOI-prefix hints, year, journal, page, limit, are documented in-schema). The description adds no parameter meaning beyond what the schema already states, 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?

The description names a specific verb (Search) and a well-scoped resource (peer-reviewed Chinese scientific research dossiers in SinoGreenTech, with parenthetical domain scoping to Clean Energy, EV Batteries, Energy Storage & Grid Engineering). An agent can tell this is a discovery/search tool rather than a retrieval tool, though it never names or contrasts with siblings like get_paper_dossier.

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: 'Search ... dossiers' plus the mention of DOIs and abstracts suggests discovery-then-detail workflows, and the domain parenthetical narrows scope. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g. when to prefer get_paper_dossier for a known DOI), so an agent must infer routing.

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