Skip to main content
Glama
dsh-lit-search-mcp

dsh-lit-search-mcp

by Flan246

lit_search

Read-onlyIdempotent

Search academic papers by keyword across Crossref, OpenAlex, and Semantic Scholar, returning merged, deduplicated results with DOI and citation counts.

Instructions

Search academic papers on Crossref, OpenAlex and Semantic Scholar by keyword. Returns merged, deduplicated results with DOI and citation counts.

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

Input Schema

NameRequiredDescriptionDefault
sortNocitations (default) | date | relevance
limitNoMax results (default 10)
queryYesSearch keywords
year_toNoLatest publication year
year_fromNoEarliest publication year

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description does add real behavioral value beyond that: it discloses federated querying across three sources and that results are merged and deduplicated, which explains why counts may differ from a single-source search. It does not cover partial-source failure or rate-limit behavior, so it stops short of a 4.

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?

Two tight sentences with the action and sources front-loaded and the return shape second. No filler, no repetition of schema fields.

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?

With no output schema, the description usefully characterizes the return payload (merged, deduplicated, DOI and citation counts), which is what an agent needs to decide downstream use. Minor gaps remain around default source coverage and behavior when a source errors.

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 100%, so the schema already documents query, sort enum, limit and the year range parameters. The description adds only 'by keyword', which restates the query parameter and contributes nothing about sort, limit, or year filtering; baseline 3 applies.

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?

States a specific verb and resource ('Search academic papers') and names the three upstream sources (Crossref, OpenAlex, Semantic Scholar) plus the merge/dedup behavior. It is clear what the tool does, though it never explicitly distinguishes itself from siblings lit_related or lit_cite.

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 when-to-use or when-not-to-use guidance, and no alternatives are named. An agent must infer from 'by keyword' that this is the entry-point search tool rather than a citation or related-work lookup.

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

Deploy Server

Other Tools