Skip to main content
Glama
Sign In

PropPassCheck

by com.proppasscheck
OverviewDiscussionsAdmin

Find prop firm challenges

list_challenges
Read-only

Lists the prop firm accounts PropPassCheck tracks (evaluation challenges and instant funding), each with its id, targets, loss limits, price and the date the rules were last checked. Filter by firm, account type, market, drawdown type, price and the rules a trading style needs (no daily loss limit, no consistency rule, weekend holding, news trading).

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_challenges"
  }
}

Input Schema

NameRequiredDescriptionDefault
firmNoPart of a firm name, for example "FTMO". Leave out for all firms.
typeNoAccount type.
marketNoForex and CFD firms, or futures firms.
drawdownNostatic: the maximum loss never moves. trailing: it follows the account up (including ones that lock at the start).
max_priceNoOnly accounts with a recorded fee at or below this, in dollars.
news_tradingNoLeave out accounts recorded as restricting trading around news.
no_daily_limitNoOnly accounts with no daily loss limit.
weekend_holdingNoLeave out accounts recorded as not allowing trades held over the weekend.
no_consistency_ruleNoOnly accounts with no best-day consistency rule.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful context beyond annotations: it lists the fields returned (id, targets, loss limits, price, date rules last checked) and clarifies that filters include trading-style requirements, which helps an agent understand the output and filtering behavior.

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 wording. The first sentence front-loads what the tool returns, and the second groups all filter dimensions efficiently. The structure is easy for an agent to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter, read-only list tool with no output schema, the description is fairly complete: it names the returned fields and explains filter intent. It does not mention pagination, ordering, default result limits, or behavior when no matches are found, which would be helpful for an agent to know before calling.

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 description coverage is 100%, so the schema already documents every parameter. The description enumerates the same filter categories (firm, type, market, drawdown, price, rule flags), adding only minor framing but no syntax or format details beyond what the schema provides. The baseline of 3 applies when the schema does the heavy lifting.

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 states a specific verb (lists) and resource (prop firm accounts PropPassCheck tracks, including evaluation challenges and instant funding), and enumerates the returned fields. It does not explicitly distinguish itself from siblings like get_challenge or compare_challenges, but the listing scope is clear.

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 explains that you can filter by firm, account type, market, drawdown type, price and trading-style rules, which implies the tool's use for searching/filtering challenges. However, it gives no explicit guidance on when to choose this over alternatives such as compare_challenges or find_best_size, nor does it state any when-not conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PropPassCheck toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources