Skip to main content
Glama

Firecrawl by Nova (CIVAI)

alexandria_library_read

Run capabilities of Alexandria data providers and return their typed, sourced records: one, or up to ten in one call when a task needs several lookups. Alexandria is Firecrawl's library of data providers across companies, people, jobs, finance and filings, public records and government spending, real estate, places and restaurants, retail and prices, package registries and developer data, news, research, and more. For people and company enrichment or search, use people_company_enrich or people_company_search when they are listed, and for job postings use jobs_search when it is listed; call a provider here directly only when the user asks for that provider. Each entry of calls is {provider, capability, options}: provider and capability come from firecrawl_search results or alexandria_library_search, and options follow the capability's contract, which marks required inputs and any requiresOneOf groups (at least one member per group). Where the contract declares pagination, its fields page through results with the same filters. Returns one result per call, in the same order, in data.alexandria, each with data, records, or an error with a code; one call can fail while the others succeed, and an invalid call returns an error naming the valid options. A result too large to return inline is retained, and nextTool reads it in slices. Billed per executed capability; discovery is free. Some providers require accepted terms; when a response reports a terms requirement, direct the user to the Firecrawl dashboard URL in that response.

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": {
      "calls": "<calls>",
      "objective": "<objective>"
    },
    "name": "alexandria_library_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
callsYesThe capabilities to run, 1-10, each {provider, capability, options}. Results come back in the same order.
timeoutNoExecution timeout in milliseconds.
objectiveYesThe 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.
requestIdNoIdempotency key bound to one execution payload. Generated when omitted and returned with the result.
conversationIdNoconversationId from any earlier Firecrawl tool result in this conversation; after parallel calls, any one of theirs. Omit only on the first call of a conversation; the result returns one to pass on every later call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / objective / description
      Previous value: -"The user's underlying goal for this call, in one sentence: what they are ultimately trying to accomplish, not a restatement of the URL or query. Reuse it across related calls. Avoid sensitive information."New value: +"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."
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does most of it: per-call error codes, partial failure across a batch, an invalid call naming valid options, ordering guarantees, oversized results retained for nextTool slicing, per-executed-capability billing with free discovery, and terms requirements with a dashboard URL. It stops short of describing auth or rate limiting beyond the terms note.

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?

The purpose and the primary routing advice are front-loaded, and most sentences carry distinct operational facts. It is dense rather than padded, though the long domain enumeration and compressed multi-clause sentences make it heavier to parse than needed.

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?

Despite no output schema, the description fully specifies the return contract: one result per call in the same order under data.alexandria, each with data, records, or a coded error. Combined with the batching limit and discovery prerequisite, an agent has everything required to call it correctly.

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 coverage is 100%, so the baseline is 3. The description adds real meaning for the nested `calls` shape (provider and capability must originate from search results; options follow the capability contract and its requiresOneOf groups; pagination fields reuse the same filters), but says nothing about timeout, requestId, conversationId, or objective — the schema descriptions handle those.

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?

Opens with a specific verb and resource: 'Run capabilities of Alexandria data providers and return their typed, sourced records', plus scope (one, or up to ten per call). It also characterizes the provider library by domain and names the siblings it is not (people_company_enrich, people_company_search, jobs_search).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing: use people_company_enrich/search for people and company work, jobs_search for job postings, and call a provider here 'only when the user asks for that provider'. It also states that provider/capability values come from firecrawl_search or alexandria_library_search, so the discovery step is unambiguous.

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