Skip to main content
Glama

Firecrawl by Nova (CIVAI)

firecrawl_provider_directory

List every Alexandria data provider, or every provider in one category, in a single call; with limit, only the first providers in catalogue order. Used by the Firecrawl sidebar; free, and it executes no provider. Use alexandria_library_search to browse the catalogue or read contracts (/library///.md).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "firecrawl_provider_directory"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoReturn only the first providers, in one catalogue page.
categoryNoCategory ID (the <category> folder in alexandria_library_search's /library).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"Category ID from the firecrawl_find_tools category index."New value: +"Category ID (the <category> folder in alexandria_library_search's /library)."
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses that the call is free, executes no provider, and completes in a single call, plus the ordering semantics of limit. It omits the return shape (no output schema exists) and what happens with an unknown category ID, so the behavioral picture is incomplete for an unannotated tool.

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?

Two sentences, front-loaded with the core action and scope before the sidebar/alternative guidance. Slightly dense with parenthetical path syntax, but no filler.

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?

For a simple, two-optional-parameter read tool with no annotations and no output schema, the description covers what it returns (provider listings), the scope options, cost model, and the sibling to use for browsing. Only the response shape and invalid-category behavior remain unaddressed.

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 baseline is 3. The description reinforces that 'limit' returns the first providers in catalogue order and that 'category' selects a single category, but adds no syntax or format detail beyond what the schema already documents.

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?

States a specific verb and resource ('List every Alexandria data provider') plus the exact scope variants (all providers, or one category, in a single call). It also implicitly separates itself from alexandria_library_search by framing this as a flat directory enumeration rather than a catalogue browse.

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?

Explicitly names the alternative ('Use alexandria_library_search to browse the catalogue or read contracts') and gives the context for this tool (Firecrawl sidebar, free, executes no provider). It stops short of stating an explicit when-not condition, but the routing intent is clear.

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