Skip to main content
Glama

search_snippets

Semantic Scholar: search INSIDE paper full text and return matching text snippets (not just titles/abstracts).

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": {
      "query": "<query>"
    },
    "name": "search_snippets"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
max_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations and no output schema, the description carries the full disclosure burden. It does add that results are full-text snippets rather than metadata, but it says nothing about which papers are searchable, rate limits, result ordering, or what fields a snippet contains — the things an agent most needs to interpret results.

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 tight sentence with the key distinction front-loaded after the 'Semantic Scholar:' prefix. No wasted wording; slightly more structure could separate what it searches from what it returns.

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 search tool the description covers purpose and return shape, which is the core. However, absent annotations and an output schema, an agent still lacks any statement about corpus coverage or result limits before committing to a call.

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 0%, so the description should compensate, and it says nothing about 'query' syntax or the 'max_results' cap or default. The mitigation is that both parameter names are essentially self-explanatory, so the practical ambiguity is small.

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 gives a specific verb ('search INSIDE') and resource ('paper full text') and states the return type ('matching text snippets'). The parenthetical '(not just titles/abstracts)' implicitly separates it from title/abstract search tools like search_papers, though it does not name the sibling 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 implied rather than stated: use this when you need full-text matches instead of titles/abstracts. There is no explicit 'use X instead when...' routing, no mention of coverage constraints (e.g., open-access availability), and no exclusions.

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.