Skip to main content
Glama
Sign In
Scout MCP Server

Scout MCP Server

Official
by Scout-AI-Labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

scout_extract

Extract structured data from multiple URLs by describing your objective in plain language.

Instructions

Extract structured data from one or more URLs. Provide an objective describing what to pull.

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": {
      "urls": "<urls>"
    },
    "name": "scout_extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesURLs to extract from
objectiveNoWhat to extract, in plain language

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided, so description alone must convey behavioral traits. It only states 'extract structured data' without indicating side effects, rate limits, or output format, leaving significant gaps.

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 clear, concise sentences with no superfluous content. Essential information is front-loaded.

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?

Given the tool has no annotations and no output schema, the description should provide more context about return values, error handling, or multi-URL behavior. It currently covers only basic input guidance.

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% and description adds minimal nuance ('Provide an objective describing what to pull') that largely restates the schema's own description. No additional semantic value beyond schema.

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?

Description states 'Extract structured data from one or more URLs', clearly identifying the tool's function. However, it does not explicitly differentiate from sibling tools like scout_scrape or scout_crawl, which share similar extraction purposes.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives. The description only mentions providing an objective, but does not specify contexts or exclusions relative to other scout tools.

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

Deploy Server

Other Tools