SimpleFunctions

monitor_the_situation

Monitor situations by scraping web content, analyzing with an LLM, and cross-referencing prediction markets for insights. Use for scheduled or one-shot URL ingestion with optional analysis and market enrichment.

Instructions

End-to-end pipeline: scrape one or more URLs (or run a search/crawl/map/extract), optionally analyze with an LLM against a prompt + JSON schema, optionally cross-reference with prediction markets, and return the bundle. Side-effectful (calls Firecrawl + LLM, billed). Requires SF API key. Use for scheduled or one-shot URL ingestion; use enrich_content if you already have the text in hand.

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": {
      "apiKey": "<apiKey>",
      "source": "<source>"
    },
    "name": "monitor_the_situation"
  }
}

Input Schema

Name	Required	Description
`apiKey`	Yes	SF API key (sf_live_...). Required.
`source`	Yes	Source configuration. Exactly one of url/urls/query must be set, matching the chosen action.
`analysis`	No	LLM analysis step. Omit to skip.
`enrich`	No	Market enrichment step. Omit to skip.

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedv0.1.2Apr 7, 2026

addedInput schema / properties / analysis / description
```
Added value: +"LLM analysis step. Omit to skip."
```
addedInput schema / properties / analysis / properties / enabled / description
```
Added value: +"Set true to run LLM analysis on scraped content."
```
addedInput schema / properties / analysis / properties / model / description
```
Added value: +"LLM model id. Default: gemini-2.5-flash."
```
addedInput schema / properties / analysis / properties / prompt / description
```
Added value: +"LLM prompt. Required when enabled."
```
addedInput schema / properties / analysis / properties / schema / description
```
Added value: +"Optional JSON schema for structured output."
```

addedInput schema / properties / apiKey / description

Added value: +"SF API key (sf_live_...). Required."

addedInput schema / properties / enrich / description

Added value: +"Market enrichment step. Omit to skip."

addedInput schema / properties / enrich / properties / enabled / description

Added value: +"Set true to cross-reference scraped content with prediction markets."

addedInput schema / properties / enrich / properties / topics / description

Added value: +"Topic hints for the market search. Required when enabled."

addedInput schema / properties / source / description

Added value: +"Source configuration. Exactly one of url/urls/query must be set, matching the chosen action."

addedInput schema / properties / source / properties / action / description

Added value: +"Firecrawl action. Required. \"scrape\"=single url, \"batch_scrape\"=multiple urls, \"crawl\"=follow links, \"search\"=web search by query, \"map\"=site map, \"extract\"=structured extraction."

addedInput schema / properties / source / properties / options / description
```
Added value: +"Pass-through options forwarded to Firecrawl."
```
addedInput schema / properties / source / properties / query / description
```
Added value: +"Search query. Required for action=search."
```

addedInput schema / properties / source / properties / url / description

Added value: +"Single URL. Required for action=scrape/crawl/map/extract."

addedInput schema / properties / source / properties / urls / description
```
Added value: +"URL list. Required for action=batch_scrape."
```

Addedv0.1.0Apr 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Without annotations, description carries burden. It discloses side effects (calls Firecrawl + LLM, billed) and auth requirements (SF API key). However, it does not detail the return bundle structure or potential error states, leaving some behavioral aspects implied.

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?

Description is a single, well-structured paragraph. First sentence defines purpose, second covers side effects and requirements, third gives usage guidance. No redundancy, every sentence adds value.

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?

Given tool complexity (multi-step, optional components), description is fairly complete: covers actions, optional steps, trade-offs. Return format is not described (no output schema), but context signals indicate no output schema, so burden is on description. Description could be more explicit about the bundle contents.

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 schema already documents all parameters. The description adds context by naming the optional analysis and enrichment steps but does not provide significant new meaning beyond what the schema offers. Baseline 3 is appropriate.

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?

Description clearly defines the tool as an end-to-end pipeline for scraping URLs (or search/crawl/map/extract) with optional LLM analysis and prediction market enrichment. It distinguishes itself from the sibling 'enrich_content' by specifying that this tool is for URL ingestion, not for already available text.

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?

Explicitly states when to use: 'Use for scheduled or one-shot URL ingestion' and when not: 'use enrich_content if you already have the text in hand.' Also notes side effects and billing, providing clear context for decision-making.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server