Skip to main content
Glama

PropPassCheck

Prop firm list prices and price changes

price_history
Read-only

List prices with the date tracking began, the lowest list price in the last 30 days and every price change the firm made. Name challenge ids or a firm, or leave both out for every account whose list price changed in the last 90 days. List prices only: PropPassCheck does not track discount codes or use affiliate links.

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": "price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
firmNoOr: part of a firm name, to test that firm's accounts. Leave both out to rank every account.
challenge_idsNoUp to 10 PropPassCheck account ids.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds genuinely new behavioral context: the data is list prices only (no discount codes, no affiliate links) and the default result set is constrained to a 90-day change window, neither of which is derivable from the annotations.

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 dense sentences, front-loaded with the return contents followed by the invocation options and then the data scope. Every sentence carries information, though the 'does not use affiliate links' clause is more brand disclosure than agent-relevant guidance.

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?

With only two optional parameters, no output schema and annotations covering the safety profile, the description is nearly sufficient: it names the returned fields and the default scope. The remaining gap is operational rather than semantic — no mention of result size or pagination when the call covers every account changed in 90 days.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema omits: it clarifies that challenge ids refer to PropPassCheck accounts and reframes the omitted-parameter case as every account whose list price changed in the last 90 days (the schema only says 'rank every account'), which materially changes expectations about the result set.

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 opens with a specific verb and resource ('List prices') and then enumerates exactly what is returned: the date tracking began, the lowest list price in the last 30 days, and every price change. The scope sentence ('List prices only: does not track discount codes or use affiliate links') clearly separates this resource from adjacent ones like rule_changes or list_challenges.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit invocation modes — supply challenge ids, supply a firm, or omit both — and states the fallback behavior ('every account whose list price changed in the last 90 days'), so the agent knows what the no-argument call does. It stops short of naming when a sibling such as rule_changes should be used instead, so there is no true exclusion 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.

Resources