Skip to main content
Glama

Firecrawl by Nova (CIVAI)

firecrawl_monitor_get

Retrieve one monitor by ID, including its configuration and current state. This does not run or modify the monitor.

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
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

A3.6/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 behavioral burden, and it does disclose the most important trait: this is a non-mutating read that will not trigger a monitor run. It says nothing about failure behavior for an unknown ID, permission or auth requirements, or payload size, so the safety profile is only partially covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, the retrieval scope is front-loaded, and the read-only caveat follows immediately. There is no filler, no restatement of the tool name, and every clause carries information.

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 single-record read with no output schema, the description is nearly sufficient: it names the two things returned (configuration and current state) so the agent knows what to expect. The remaining gaps, ID provenance and error behavior on a bad ID, are modest but real.

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 50%: the objective parameter is well documented in the schema, but the required id parameter has no schema description at all. The description only says "by ID" and adds no format hint or pointer to where an ID comes from (e.g., firecrawl_monitor_list), so it does not compensate for the coverage gap. A 3 is the baseline for this coverage level.

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 uses a specific verb ("Retrieve") and a clearly bounded resource ("one monitor by ID") and states what is returned ("its configuration and current state"). The phrase "does not run or modify the monitor" implicitly separates it from firecrawl_monitor_run and firecrawl_monitor_update, though no sibling is named explicitly, so it stops short of a full 5 on differentiation.

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?

The negative clause "This does not run or modify the monitor" tells the agent what this tool is NOT for, which is useful routing guidance. However, it never names the alternative to use instead (firecrawl_monitor_run, firecrawl_monitor_update) or the condition that should send an agent to firecrawl_monitor_list or firecrawl_monitor_check, so the when-to-use rule is only implied.

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