scan_sample
FREE — pick-of-the-day: a full-depth sample of the sports engine on one featured matchup. No auth, no payment.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
signalpulse-mcp
TDQS
A3.6/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses that the tool is free, requires no auth/payment, and returns a sample of one matchup. However, it does not explain what 'full-depth sample' includes, output format, or any limitations beyond the single matchup.
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, tightly-worded sentence that front-loads the 'FREE' hook and quickly conveys the purpose and access requirements. Every word contributes value with no redundancy.
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's extreme simplicity (0 params, no annotations, no output schema), the description is somewhat adequate but leaves ambiguity about what 'full-depth sample' contains and what sports are featured. It could clarify the nature of the data returned.
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?
The tool has zero parameters, so the description need not add parameter details. Baseline for 0 params is 4, and the description correctly implies no input is needed ('pick-of-the-day').
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 that this tool provides a free sample of the sports engine on one featured matchup. It uses a specific verb ('scan' implied by the name, and 'sample') and distinguishes itself from sibling scan_* tools by being a free 'pick-of-the-day' preview.
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?
It implies usage for a free trial or demo by emphasizing 'FREE' and 'No auth, no payment', but does not explicitly contrast with alternatives like scan_compare or signal_sports. It gives context (sports engine, one matchup) but lacks clear when-not-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3.1/5.0
Disambiguation2/5
There is significant overlap between scan_* and signal_* tools for the same underlying asset classes, e.g. scan_futures vs signal_futures, scan_racing vs signal_racing, and scan_predmarket vs signal_polymarket. Broader catch-alls like analysis, scan_ask, backtest, and signal_generate also blur the boundary, forcing an agent to parse long pricing details before knowing which tool actually applies.
Naming Consistency4/5
The overwhelming majority of tools follow a clear `scan_` or `signal_` snake_case prefix, which makes the product families easy to recognize. A small set of standalone unprefixed tools — analysis, backtest, instruments, leaderboard, quote, track_record — breaks the pattern, but the overall scheme is still consistent enough to infer.
Tool Count2/5
47 tools is far beyond the practical range for an agent to reason about, even though the server's domain is broad and heavily segmented. Many specialist endpoints could be consolidated under fewer catch-all scanners and signals, but the exposed surface instead forces a large tool-selection decision on every request.
Completeness4/5
The tool surface covers discovery, cost preview, sample analysis, public track records, leaderboards, broad market scanning, asset-class-specific scanning, sports and event signals, and prediction-market verticals. There are minor gaps in explicit account/credit management and some redundant paths, but for a signal/research service the workflow is largely complete.