get_deals
Get currently visible PropScorer promo codes and deals, ranked by discount and public availability.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| category | No | futures |
PropScorer
TDQS
A3.6/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full transparency burden. It discloses some behavioral traits: 'currently visible' implies deals may change or be filtered, and 'ranked by discount and public availability' explains ordering. However, it does not mention any limitations, rate limits, authentication, or what happens when no deals are found.
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, concise sentence that front-loads the core purpose and key behavior. It contains no redundant information and is appropriately sized for the tool's simplicity.
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 two optional parameters and no output schema. The description gives the essence but lacks explanation of the return format and parameter semantics. It is minimally viable but leaves some context gaps, particularly for an agent expecting detailed invocation guidance.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate but does not mention 'limit' or 'category' at all. The schema provides types, defaults, and an enum, but the semantic meaning of 'category' (e.g., futures vs crypto) is not explained anywhere. The agent must infer parameter meaning from param names alone, which is insufficient for full clarity.
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's function: 'Get currently visible PropScorer promo codes and deals' with a specific verb and resource. It also adds unique qualifiers ('ranked by discount and public availability') and distinguishes from all sibling tools, which focus on firm comparison and rules rather than deals.
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 does not explicitly state when to use this tool or mention alternatives. However, from the sibling tool names, it is clear that this is the only tool for deals/promo codes, so usage is implied. There is no misleading guidance, but also no explicit context.
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
Disambiguation4/5
Most tools have clearly distinct purposes, but a few overlaps exist: search_firms and find_firms_by_rules both support rule-based search, and compare_firms vs compare_firm_rules vs rank_firms_for_trader_profile all involve comparing multiple firms though with different focuses. Descriptions are detailed enough to guide selection in most cases.
Naming Consistency5/5
All tool names follow a consistent snake_case verb_noun pattern (get_, compare_, search_, rank_, etc.). The verbs clearly indicate the action and the nouns indicate the target, making the set predictable and easy to navigate.
Tool Count5/5
With 11 tools, the server is well-scoped for a prop firm analysis domain. Each tool serves a distinct function from searching and scoring to comparing, ranking, and answering complex questions, without excessive overlap or unnecessary proliferation.
Completeness5/5
The tool set covers the full lifecycle of prop firm evaluation: finding firms, retrieving scores and rules, comparing firms, ranking by trader profile, accessing deals, payout intel, and KB freshness. It also includes a general Q&A tool for complex queries, filling any potential gaps. No major missing operations are apparent.