Skip to main content
Glama

Compare with published literature / 与已有文献对比

literature_compare

Compare with published literature / 与已有文献对比 | USE WHEN: the user wants to know how their findings differ from what is already published | ALIASES: 和文献比, 新在哪, 对比已有研究, literature compare, how is this different | 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": {
      "title": "<title>"
    },
    "name": "literature_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes标题
main_findingsNo主要发现

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Added

TDQS

B3.4/5.0
Behavior2/5

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

The annotations already cover the structure and safety profile: readOnlyHint=false, openWorldHint=false, destructiveHint=false. The only additional information is 'RETURNS: 对比结论' (comparison conclusion), which is vague. The definition does not say where the 'published literature' comes from, whether the tool performs a search, or what the comparison actually produces. This is notable given openWorldHint=false, which implies an internal corpus.

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 sections are front-loaded and compact, with the USE WHEN information placed before the aliases. The alias list is somewhat noisy but plausibly useful for matching user phrasing.

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 two-parameter comparison tool with no output schema, the definition covers the trigger and a one-line return hint but leaves unclear what literature source is used and what the comparison output contains. It is adequate but has real gaps.

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 both parameters (title and main_findings) are already documented in the schema. The description adds no format, length, or content guidance beyond that, so the baseline of 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 definition states a specific verb and resource ('Compare with published literature') and the USE WHEN clause clarifies the scope as 'how their findings differ from what is already published'. It does not differentiate itself from the similarly named sibling local_literature_compare, 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 Guidelines4/5

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

The USE WHEN clause gives a concrete triggering condition tied to the user's intent, which is more than most definitions offer. It names no exclusions or alternative tools, however, which is especially relevant given the near-identical sibling name.

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