Skip to main content
Glama
Sign In
Scout MCP Server

Scout MCP Server

Official
by Scout-AI-Labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

scout_answer

Answer a natural-language question by reading a webpage and the pages it links to.

Instructions

Answer a natural-language question by reading a page and the pages it links to.

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": {
      "url": "<url>",
      "question": "<question>"
    },
    "name": "scout_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe page to read
questionYesThe question to answer

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses that the tool reads linked pages, which is useful, but does not specify depth, auth needs, or output format.

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?

The description is a single, efficient sentence that conveys the core purpose without any superfluous words.

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 two simple parameters and no output schema, the description is fairly complete. It explains the tool's behavior and context. However, it could mention the return format to improve actionability.

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

Parameters4/5

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

Schema coverage is 100% with basic descriptions for url and question. The description adds meaning by explaining that the url is the starting page and that linked pages are also read, which goes beyond the 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?

The description clearly states the tool answers a natural-language question by reading a page and its linked pages. It distinguishes from siblings like scout_extract (structured extraction) and scout_scrape (raw content) but could be more explicit about the Q&A nature.

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 description implies usage for question-answering from a page and its linked pages, but provides no explicit guidance on when to use vs alternatives like scout_search or scout_extract.

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