Skip to main content
Glama

Firecrawl by Nova (CIVAI)

firecrawl_monitor_checks

List historical checks for a monitor, optionally filtered by status and bounded by a result limit. Returns one page of check summaries and pagination metadata.

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": {
      "id": "<id>"
    },
    "name": "firecrawl_monitor_checks"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
limitNo
offsetNo
statusNo
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.2/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 does useful work by disclosing that results are paginated ('one page') and that the response contains check summaries plus pagination metadata, which tells the agent to loop on offset. It omits permission requirements, rate limits, ordering of historical checks, and whether any data is mutated (read-only is only implied by 'List').

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 compact sentences with the resource and scope front-loaded and no filler. Nothing is redundant, though the brevity is partly the cause of the parameter gaps rather than a virtue in itself.

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?

With no output schema and no annotations, the description does cover the return shape (one page of check summaries plus pagination metadata), which is the most valuable missing piece. However, for a five-parameter tool at 20% schema coverage, leaving offset and the required id unexplained is a meaningful omission.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20%, so the description must compensate and largely does not. It explains the status filter and the result limit in passing, but says nothing about the required 'id' (presumably the monitor identifier), nothing about 'offset' semantics despite referencing pagination, and nothing about the unusual 'objective' parameter, whose schema text describes a data-sharing purpose an agent could easily misuse.

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?

The description gives a specific verb and resource ('List historical checks for a monitor') plus the scope of the result set, which implicitly separates it from the singular firecrawl_monitor_check sibling. It stops short of explicitly naming that sibling or stating the distinction, so it is clear but not maximally differentiating.

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?

Usage is only implied: an agent can infer this is the paginated-history tool versus the single-check tool, and the mention of a status filter suggests a triage workflow. There is no explicit when-to-use or when-not-to-use guidance, and no pointer to firecrawl_monitor_check or firecrawl_monitor_get as alternatives.

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