OpenPapers

Research method

research_method

Search verified literature for a named method. Results include evidence and provider transparency for each source.

Instructions

Search verified literature for a named method with provider transparency and evidence.

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": {
      "method": "<method>"
    },
    "name": "research_method"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`method`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 2, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose a read-oriented search behavior and hints at output traits ('provider transparency and evidence'), which adds some context. However, it does not explain what 'verified literature' means, whether results are curated, or any limitations or side effects.

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 description is a single compact sentence with the main action front-loaded, and there is no filler or repetition. It is concise, though the compressed phrase 'with provider transparency and evidence' could be clearer.

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

Completeness2/5

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

For a tool with no annotations, no output schema, and many closely related sibling tools, the description is too sparse. It does not explain return value shape, the meaning of 'verified', the 'limit' parameter, or how this tool relates to the many other search/compare tools in the family.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, so the description must compensate. It clearly implies the meaning of 'method' as a named method to search for, but it does not explain the 'limit' parameter at all, leaving one of the two parameters semantically undocumented.

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 action ('Search'), a resource ('verified literature'), and a target ('a named method'), which is clear enough to differentiate it from generic paper search. However, it does not explicitly distinguish it from siblings like search_papers or vector_search, and the phrase 'provider transparency and evidence' is vague.

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?

The description gives no explicit guidance about when to use this tool versus alternatives such as search_papers, research_topic, compare_methods, or vector_search. The intended use case is only implied by the wording, with no when-to-use or when-not-to-use direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.