Construction opportunity intelligence for AI agents, providing structured project discovery and previews for Northeast Ohio contractors and service providers.
Scored across 2 tools
The two tools serve clearly distinct purposes: one explains the service and its capabilities, the other provides preview data. There is no overlap or ambiguity between them.
Both tools use a verb_noun pattern with 'scout' as a common prefix, making them consistent. The slight deviation is that one verb is 'scout' and the other is 'preview', but the pattern is clear and predictable.
With only 2 tools, the server feels thin for a domain like opportunity discovery, which typically requires multiple actions (search, filter, retrieve details). The preview is limited to 3 results, so the tool set is under-scoped for its intended purpose.
The server provides only a capability overview and a limited preview, lacking core operations like full search, filtering, or detailed retrieval. The preview intentionally withholds details, creating a dead end without paid tools, so the surface is incomplete for practical use.
Describe Opportunity Atlas coverage, freshness, available tools, and planned premium pricing. Use this first to understand what Scout can answer.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. The verb 'Describe' and 'Use this first' signal a read-only, informational call, and the listed content (coverage, freshness, tools, planned pricing) clarifies what behavior/returns to expect. It stops short of explicitly stating no side effects or data changes, but this is low-risk for a zero-argument overview tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short, front-loaded sentences with no filler. The first states the action and scope; the second gives the recommended invocation order and expected benefit.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter capability-overview tool, the description is essentially complete: it names the subject, the content areas, and the recommended usage position. It does not describe the output structure, but no output schema exists and the listed content areas approximate what the response will cover.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are no parameters, so the schema leaves nothing to explain. The description still adds value by enumerating the content dimensions the tool covers ('Opportunity Atlas coverage, freshness, available tools, and planned premium pricing'), which orients the agent to what the result will contain.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific verb and resource: 'Describe Opportunity Atlas coverage, freshness, available tools, and planned premium pricing.' It clearly names the tool's role as a Scout capabilities/overview entry point and distinguishes it implicitly from the sibling scout_preview by saying to use it first.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly tells the agent when to use it: 'Use this first to understand what Scout can answer.' This gives clear context for a first-step capability tool, though it does not spell out when not to use it or name scout_preview as the follow-up alternative.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Free redacted preview of matching Northeast Ohio construction opportunities. Returns up to 3 results; full intelligence and contact paths are intentionally not exposed in preview.
| Name | Required | Description | Default |
|---|---|---|---|
| city | No | ||
| limit | No | ||
| stage | No | ||
| trade | No | ||
| county | No | ||
| min_score | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavioral traits. It mentions the redacted nature and the limit of 3 results, which is helpful. However, it does not explain what 'full intelligence' entails, why it is intentionally hidden (e.g., requiring a paid subscription), or any limitations like response format or performance. The description gives a hint but is not sufficiently transparent for a tool that is clearly a teaser.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise, using two sentences that directly state the tool's purpose and key constraints. Every sentence adds value, and it is appropriately front-loaded with the main function. No fluff or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has 6 parameters, no annotations, and no output schema, the description is insufficient. It does not explain what the preview includes beyond redaction, what the response format is, or how parameters affect the search. The sibling tool 'scout_capabilities' might provide context, but the description does not leverage it. The description is too brief for a tool with this complexity, leaving many gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description provides no explanation of any parameters. The tool has 6 parameters (city, limit, stage, trade, county, min_score) and the description only mentions that it returns up to 3 results, which aligns with the 'limit' parameter's max, but does not explicitly link them. The agent is left to infer the semantics from names alone, which is inadequate for complex parameters like 'min_score' and 'stage'.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states the tool provides a 'free redacted preview of matching Northeast Ohio construction opportunities,' which is a specific verb (preview) and resource (construction opportunities). However, it doesn't explicitly differentiate from the sibling tool 'scout_capabilities' beyond the preview aspect, leaving some ambiguity about when to use each.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for getting a preview of opportunities but does not provide explicit guidance on when to use this tool versus scout_capabilities. It mentions the free and redacted nature, but no exclusions or alternatives are named, making it clear but not comprehensive.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
scout_capabilitiesscout_preview
Add one secure layer between your agents and this server.
