Skip to main content
Glama
science-ai-mcp-server

science-ai-mcp-server

by SelfPy

Research Gaps: Free Literature Search

find_research_gaps

Search research literature for field overviews and closest, cited, and recent papers to scope early-stage topics; unlock actual gap analysis in the web app.

Instructions

Free literature search on a research topic — spends no credits and makes no LLM call; rate-limited to 10 searches/hour per IP. Returns a field overview and the papers the search found: the closest matches from a 7.9M-paper local library, plus the most-cited and most-recent work on the topic. It does NOT return research gaps: the response carries gaps: [] and gapsLocked: true. Gaps come from unlocking the topic in the web app at scienceaijournal.com/research-gaps — one charge of 50 credits that also includes the filled comparison table, a research proposal and one Pro Report run. Use for early-stage literature discovery and proposal scoping.

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

Input Schema

NameRequiredDescriptionDefault
fieldNoOptional field bias (e.g. 'computer_science', 'biology').
queryYesResearch topic (≥ 4 chars). A full phrase finds sharper results than a single word; a title + abstract joined by a newline also works.
departmentIdNoOptional departmentId to enable methodology-alignment hints for your discipline's vocabulary.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.4
    • changedInput schema / properties / departmentId / description
      Previous value: -"Optional departmentId to enable methodology-alignment hints (boosts gaps whose text matches your discipline's KPI / question vocabulary)."New value: +"Optional departmentId to enable methodology-alignment hints for your discipline's vocabulary."
    • changedInput schema / properties / query / description
      Previous value: -"Research query (≥ 10 chars). Free-form prose or a title + abstract joined by newline."New value: +"Research topic (≥ 4 chars). A full phrase finds sharper results than a single word; a title + abstract joined by a newline also works."
    • changedInput schema / properties / query / minLength
      Previous value: -10New value: +4
  2. First observedv0.1.3

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so thoroughly: no credit spend, no LLM call, an explicit 10 searches/hour per-IP rate limit, and a precise statement of what the response contains and lacks (gaps: [] and gapsLocked: true). This is exactly the operational context an agent needs before calling.

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?

Sentences are front-loaded with the highest-value facts (free, no LLM call, rate limit) and the negative scope before any promotional detail. The closing detail about the 50-credit web-app bundle is somewhat tangential but does serve to redirect the agent when gaps are actually wanted.

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

Completeness5/5

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

The tool is simple (1 required, 2 optional params, no output schema), and the description compensates for the absent output schema by describing the return payload and its notable locked-gaps fields. Nothing needed to call or interpret the result is missing.

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 all three parameters (query, field, departmentId) are already documented in the schema, including phrasing tips and length bounds. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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 first sentence states a specific verb and resource — a free literature search on a research topic — and immediately disambiguates from the misleading tool name by stating 'It does NOT return research gaps.' An agent knows exactly what it gets back (field overview + papers from a 7.9M-paper local library) without opening the schema.

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?

It gives an explicit use case ('early-stage literature discovery and proposal scoping') and routes the gap-seeking case elsewhere (unlock the topic in the web app). It does not compare against sibling MCP tools such as ai_review_paper or recommend_journals, so the when-not-to-use-this-instead guidance is only partial.

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