Skip to main content
Glama

Metis · Librarian — Search Semantic Scholar

search_semantic_scholar

Search Semantic Scholar's citation graph to discover papers on a topic and add them to your news briefs.

Instructions

Search Semantic Scholar for papers on a topic (citation-graph discovery).

Complements PubMed (scan_pubmed_alerts) and OpenAlex (scan_openalex) with
Semantic Scholar's 200M+ paper graph and citation counts. Free public Graph
API, no key required. Matched papers are inserted into news_briefs with
source_type='article' (domain 'Semantic Scholar') so the Librarian and the
dashboard surface them like any other discovered paper.

Args:
    query: Free-text topic to search (e.g. "HAT elimination surveillance").
           Defaults to your configured PubMed/topic query if empty.
    max_results: Maximum papers to retrieve (default 10, max 100).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNo
max_resultsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries full burden. It discloses a key side effect: matched papers are inserted into news_briefs with specific metadata. It also mentions the API is free and no key required. However, it doesn't mention rate limits, error handling, or the exact response format beyond the output schema existence.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a concise intro, a contextual paragraph, and a clean Args list. Every sentence adds value without repetition. No fluff.

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

Completeness4/5

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

Given the presence of an output schema (not shown but indicated), the description sufficiently covers the tool's purpose, behavior, and parameter details. It could be improved by briefly noting the return type or pagination behavior, but for a search tool with output schema, it is nearly complete.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate. It fully explains both parameters: query with an example and default behavior, max_results with default and maximum. This adds essential meaning beyond the raw schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool performs citation-graph discovery on Semantic Scholar, using a specific verb ('Search') and resource ('Semantic Scholar'). It distinguishes itself from siblings by explicitly naming complementary tools (scan_pubmed_alerts, scan_openalex) and highlighting the unique value of 200M+ papers and citation counts.

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 description provides clear context for when to use this tool: for citation-graph discovery and complements PubMed/OpenAlex. It mentions no API key required, but does not explicitly state when not to use it or provide strict exclusions. The guidance is strong but lacks explicit when-not-to-use instructions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SVerITG/Metis'

If you have feedback or need assistance with the MCP directory API, please join our Discord server