Skip to main content
Glama

三域医研 · 科研算法引擎 (SanYu Research Engine)

Review outline from reading list / 文献综述提纲

literature_review_outline

Review outline from reading list / 文献综述提纲 | USE WHEN: the user wants a review outline built from the papers already digested | ALIASES: 综述提纲, review outline, 按精读文献出提纲 | RETURNS: 综述提纲

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": {
      "topic": "<topic>"
    },
    "name": "literature_review_outline"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYes综述主题(必填)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / topic
      Added value: +{
      +  "description": "综述主题(必填)",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[]New value: +[
      +  "topic"
      +]
  2. Added
  3. Removed
  4. Added
  5. Removed
  6. Added
  7. Removed
  8. Added
  9. Removed
  10. Added
  11. Removed
  12. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false but destructiveHint=false and openWorldHint=false, i.e. a non-destructive generating operation; the description adds only the implicit prerequisite that digestion must have happened first. It does not explain what the non-read-only behavior means (file/database write? session artifact?), nor cost, latency, or any limits, so it leaves the main behavioral question unanswered.

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?

The pipe-delimited, label-first layout (USE WHEN / ALIASES / RETURNS) is heavily front-loaded and wastes no words. The 'RETURNS: 综述提纲' segment largely restates the tool name, which is the only filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with no output schema, the definition covers trigger and prerequisite adequately, but the RETURNS line only echoes the title rather than indicating what the outline contains or its granularity. An agent could call it correctly but cannot set expectations for the result.

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 coverage is 100% with a single required 'topic' parameter already documented as '综述主题(必填)'. The description adds no syntax, scope, or format guidance for that parameter beyond the word 'reading list', so the schema carries the meaning and 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 states a specific verb and resource ('Review outline from reading list') and qualifies the source ('from the papers already digested'), which lets an agent distinguish it from topic-driven siblings such as topic_lit_review. It stops short of naming any sibling explicitly, so differentiation still requires inference.

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

Usage Guidelines4/5

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

'USE WHEN: the user wants a review outline built from the papers already digested' gives a clear triggering condition and an implicit prerequisite (papers must already be digested). No when-not condition and no named alternative are provided, so the agent gets context but not 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.