deal_stats
Aggregate funding statistics for a recent period: deal count, total raised, sector breakdown. Free.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Lookback window in days |
deal-tools
TDQS
B3.1/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full behavioral burden. It indicates an aggregate/read operation but does not disclose data freshness, result limits, access requirements, or whether the operation is side-effect free. 'Free' is the only extra behavioral note.
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 sentences with no wasted words. The core function and output components are front-loaded, and 'Free' is a useful tag appended without clutter.
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?
The tool is simple with one optional parameter, and the schema covers parameter semantics. However, without annotations, output schema, or sibling differentiation, the agent lacks behavioral context and selection guidance, so completeness is only adequate.
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 the days parameter is fully described in the schema, so the description adds no parameter-level meaning beyond the phrase 'recent period,' which aligns with the lookback window. Baseline 3 applies.
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 uses a specific verb ('Aggregate') and names the resource ('funding statistics') with concrete output components ('deal count, total raised, sector breakdown'). It clearly states what the tool returns, though it does not explicitly differentiate from siblings like recent_raises.
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 is given on when to use this tool versus recent_raises or raise_lookup. 'Free' addresses cost, not usage context, and there are no exclusions or alternative references.
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
A3.7/5.0
Disambiguation5/5
Each tool targets a distinct query type: aggregate stats, specific company lookup, and recent raises list. There is no meaningful overlap that would cause an agent to select the wrong tool.
Naming Consistency5/5
All tool names are lowercase noun phrases using underscores (deal_stats, raise_lookup, recent_raises). The naming pattern is uniform and predictable, even though it doesn't follow a verb_noun convention.
Tool Count5/5
Three tools is well-scoped for a focused funding/deal information domain. Each tool serves a distinct purpose and no tool feels redundant or unnecessary.
Completeness4/5
The set covers the core needs of a deal research assistant: aggregate statistics, specific company verification, and recent activity. A slight gap is a lack of detailed single-deal history or advanced filtering, but the core workflows are complete.