Skip to main content
Glama

scout_report

Run a multi-source intelligence report by searching up to 18 platforms (HN, GitHub, npm, PyPI, X, Reddit, YouTube, and more) in parallel. Choose a focus preset—balanced (14 free APIs), trending, or comprehensive—or specify exact sources. Requires a query; returns structured JSON results.

Instructions

Run a multi-source intelligence report. Searches across 18 sources (HN, GitHub, npm, PyPI, X, Product Hunt, Dev.to, Hashnode, Lobste.rs, StackExchange, ArXiv, Reddit, YouTube, Zenn, Qiita, Semantic Scholar, Lemmy, GitLab) in parallel. Use 'focus' to control source selection: 'balanced' (14 free APIs), 'trending' (HN+X+PH+Dev.to+Lobsters), 'comprehensive' (all 18). Or specify exact sources. X search uses xAI Grok API (~$0.005/call). Reddit requires API keys. YouTube requires API key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query to scout across sources
sourcesNoSpecific sources to search (overrides focus)
focusNoPreset: balanced=14 free APIs, trending=HN+X+PH+Dev.to+Lobsters, comprehensive=all 18balanced
per_pageNoResults per source
Behavior5/5

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

No annotations provided, so description must fully disclose behavior. It does so by stating parallel execution across 18 sources, cost for X search ($0.005/call), dependency on API keys (Reddit, YouTube), and free vs paid sources.

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?

Concise, front-loaded with key action and scope, then efficient detail on sources, focus options, and cost/API key notes. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no annotations, the description fully covers what the tool does, how to use it (presets vs exact sources), cost implications, and dependencies. Provides enough context for an AI agent to decide when to use this versus single-source siblings.

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 covers all parameters with descriptions (100% coverage). Description adds value by explaining the 'focus' preset meanings (e.g., 'balanced=14 free APIs') and the specific API key requirements for certain sources, which go beyond basic schema.

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?

The description clearly states the tool runs a multi-source intelligence report, searching across 18 specified sources in parallel. It distinguishes itself from sibling tools by offering a unified search across multiple platforms instead of single-source searches.

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?

Provides explicit guidance on when to use focus presets (balanced, trending, comprehensive) and how to override with exact sources. Mentions key cost and API key requirements for X, Reddit, and YouTube, helping decide if alternative siblings should be used instead.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bartonguestier1725-collab/scout-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server