Skip to main content
Glama

SinoAgriTech Crop & AgriTech

Search SinoAgriTech Peer-Reviewed Studies

search_research
Read-only

Search peer-reviewed Chinese scientific research dossiers and empirical intelligence in SinoAgriTech (Crop Genetics, Smart Agriculture, Aquaculture & Soil Science). 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 beyond that by enumerating the returned fields (titles, original DOIs, abstracts, key takeaways, enrichment version V1/V2.1, canonical URLs), which matters because there is no output schema. It omits ranking behavior, result-count behavior, and any rate/coverage caveats.

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 search purpose followed by the return shape. No filler or marketing padding. The parenthetical domain list is dense but earns its place by scoping coverage.

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?

For a 5-parameter, read-only search tool with no output schema, the description covers both what is searched and what comes back, which is the critical gap it needed to fill. Missing only secondary details such as result ordering and whether abstracts are always present.

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 query, year, journal, page and limit are all documented in the schema with formats and bounds. The description adds nothing parameter-specific — no explanation of how the query string is matched, whether filters combine conjunctively, or how journal partial matching behaves. Baseline 3 is appropriate when the schema carries the parameter burden.

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 pairs a specific verb ("Search") with a specific resource ("peer-reviewed Chinese scientific research dossiers") and scopes the subject domains (Crop Genetics, Smart Agriculture, Aquaculture & Soil Science). An agent can tell this is a keyword-search tool rather than a single-record fetch, but it never names or contrasts the siblings (get_paper_dossier, extract_empirical_tables, list_topic_hubs) explicitly.

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?

There is no when-to-use statement, no exclusion, and no pointer to an alternative tool. The agent must infer that this is the discovery entry point before get_paper_dossier, and must infer that domain/topic browsing belongs to list_topic_hubs. The purpose sentence implies usage but gives no routing guidance.

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