Skip to main content
Glama

match_paper_title

Semantic Scholar: find the single paper whose title best matches the given text (exact-match lookup).

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": "match_paper_title"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns a single best match, but does not state what happens when no match exists, whether the match is exact or fuzzy despite calling it an 'exact-match lookup', or any permission or rate-limit behavior.

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 front-loaded sentence with no wasted words. It is efficient, though the internal tension between 'best matches' and 'exact-match lookup' slightly reduces clarity.

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?

With no output schema and no annotations, the description should explain return behavior, failure modes, and matching semantics. It does not, leaving an agent without enough information to correctly interpret results when there is no exact match or when multiple papers are close.

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 schema has one parameter with 0% description coverage, so the description must compensate. It only loosely clarifies that the parameter is text to match against paper titles, and does not explain accepted formats, whether partial titles are allowed, or how matching works.

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: find the single paper whose title best matches given text. It also distinguishes itself from list/search tools by emphasizing 'single paper' and 'best matches', though it does not name any sibling explicitly. The parenthetical 'exact-match lookup' slightly muddies whether the match is exact or fuzzy.

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 explicit guidance on when to use this tool versus alternatives like autocomplete_papers, search_all, or get_paper. Usage is only implied by the phrase 'find the single paper whose title best matches the given text', leaving the agent to infer the right context.

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.