Skip to main content
Glama

Firecrawl by Nova (CIVAI)

firecrawl_research_read_paper

Retrieve in-body passages from one paper that are relevant to a specific question. Full text is available only for indexed papers; k controls the number of passages.

Returns matching passages or a notice when full text is unavailable.

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": {
      "paperId": "<paperId>",
      "question": "<question>"
    },
    "name": "firecrawl_research_read_paper"
  }
}

Input Schema

NameRequiredDescriptionDefault
kNoNumber of passages to return (default 4).
paperIdYesCanonical paperId or primaryId such as `arxiv:1706.03762`, `pmcid:PMC12530322`, `pmid:40953549`, or `doi:10.1016/j.neunet.2025.108095`.
questionYes
objectiveNoThe user's underlying goal in one sentence, not a restatement of this call's arguments. Reuse it across related calls. Firecrawl uses it to learn what agents need and improve its results. No personal data, secrets or the user's exact words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / objective
      Added value: +{
      +  "description": "The user's underlying goal in one sentence, not a restatement of this call's arguments. Reuse it across related calls. Firecrawl uses it to learn what agents need and improve its results. No personal data, secrets or the user's exact words.",
      +  "maxLength": 5000,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It does add real behavioral context: full text exists only for indexed papers and an unavailability notice is returned instead of an error, which tells an agent how to interpret an empty-ish result. It omits whether the lookup is read-only by contract, what happens with partially indexed papers, and any latency or quota behavior — notably it never mentions the telemetry use of the `objective` field that the schema itself discloses.

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?

Three short sentences with the core action front-loaded and no filler. The final sentence partly repeats the earlier indexed-papers caveat about unavailability, a small redundancy that keeps it out of the top band.

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 four-parameter, no-annotation, no-output-schema tool the description covers the essential contract (inputs, the unavailability case, return shape in outline). It leaves open the relationship to inspect_paper and how passages are delimited or ranked, which an agent would want in order to choose this tool confidently.

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 75%, with paperId, k and objective already documented in the schema, so the baseline of 3 applies. The description only restates the k behavior that the schema already spells out and adds the notion that the question should be specific, while leaving the undecorated `question` parameter largely to inference.

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: 'Retrieve in-body passages from one paper that are relevant to a specific question.' The scope (one paper, question-relevant, in-body) is precise enough that an agent knows this is not a search-across-papers tool. It stops short of naming a sibling such as inspect_paper or search_papers to differentiate further.

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?

Use is only implied by the phrase 'relevant to a specific question' — the reader must infer this is the tool for targeted content extraction from a known paperId rather than discovery or metadata lookup. There are no explicit when-to-use, when-not-to-use, or alternative-tool statements despite several plausible siblings.

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.

Resources