Skip to main content
Glama

Prop Firm Discount MCP

list_codes

List prop firm discount codes ("coupon codes" / "promo codes" to a user). Each code works any time — there is no expiry date and no validity window. Filter by firm name or minimum discount. Present results as discount codes — never as "standing codes".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_codes"
  }
}

Input Schema

NameRequiredDescriptionDefault
firmNoFirm name substring (case-insensitive).
limitNoMax rows (default 50, max 200).
offsetNoRows to skip (default 0).
min_discount_pctNoMinimum discount percentage.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / active_only
      Removed value: -{
      -  "description": "Only codes valid today (default true).",
      -  "type": "boolean"
      -}
  2. First observed

TDQS

B3.4/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 usefully discloses a real behavioral trait — codes never expire and have no validity window — which an agent could not infer from the schema. However, it says nothing about read-only safety, result ordering, or pagination behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences, front-loaded with the core action, followed by the no-expiry behavior and filtering hint. The closing style directive ("never as 'standing codes'") is slightly arbitrary but short and does not bloat the definition.

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?

For a simple read-only list tool this covers purpose, filtering, and a key domain behavior. It is missing the return shape (whether rows include firm, code, discount) and pagination expectations, which matter since there is no output schema.

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%, so all four parameters (firm, limit, offset, min_discount_pct) are already documented in the schema. The description only restates the filtering intent without adding format or semantics beyond what the schema provides, so the 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?

States a specific verb and resource ("List prop firm discount codes") and adds user-facing synonyms ("coupon codes" / "promo codes"), so the agent knows what domain object is returned. It does not explicitly distinguish itself from siblings like latest_deals or search_deals, so it stops short of a 5.

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?

"Filter by firm name or minimum discount" implies how to narrow results, but there is no explicit when-to-use / when-not guidance and no mention of the closest alternatives (latest_deals, search_deals). Usage must be inferred from the field names.

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.