Skip to main content
Glama

recommend_papers_from_examples

Semantic Scholar: recommend papers from positive (and optional negative) example paper ids.

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": {
      "positive_ids": "<positive_ids>"
    },
    "name": "recommend_papers_from_examples"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_resultsNo
negative_idsNo
positive_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing beyond the basic action. It does not say whether this is a read-only call, what permissions or API key it needs, how many results come back or how they are ranked, or what happens with invalid or unknown ids.

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?

A single front-loaded sentence with the source, verb, and mechanism in order, and no filler. It is terse rather than padded, though that terseness is what leaves the gaps noted above.

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 three-parameter tool with no annotations, no output schema, and no schema descriptions, the definition is too thin. An agent still does not know the id format, the meaning of max_results, the shape of the recommendation response, or the read-only nature of the call.

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?

Schema description coverage is 0% across three parameters, so the description must compensate and largely does not. It notes that positive ids are the anchor and negative ids are optional, but says nothing about the expected id format (Semantic Scholar id vs. DOI/arXiv), whether multiple positives are blended, or what max_results does.

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 (recommend) and resource (papers) plus the mechanism: positive and optional negative example paper ids. That clearly separates it in spirit from recommend_papers_for_paper, which works from a single seed paper, though the sibling is never named explicitly.

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: an agent can infer it should call this when it has example papers it likes (and optionally dislikes). There is no explicit when-to-use, when-not-to-use, or comparison to recommend_papers_for_paper, which is the nearest alternative.

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.