Weekly/swing gamma walls + 1σ EM on the nearest 5–45 DTE expiry (not 0DTE). Bundle/Pro.
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | No | SPY |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses key behavioral traits: the expiry selection rule, the 5–45 DTE window, the explicit 0DTE exclusion, and the Bundle/Pro access requirement.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One tight, front-loaded sentence contains all essential information: data type, expiry selection, exclusion, and access tier. There is no filler or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return shape does not need describing. The description covers the main decision-relevant details: what is returned, on which expiry, and what access is required. It only lacks explicit routing among sibling tools.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0% and the description adds no direct parameter guidance. However, the only parameter is a common 'symbol' field with a default of SPY, which is self-explanatory to an agent, so the lack of elaboration is not a major obstacle.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb and resource: it gets weekly/swing gamma walls plus 1σ EM on the nearest 5–45 DTE expiry. It also differentiates itself from intraday/0DTE tools by explicitly saying 'not 0DTE' and using 'swing'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies this is for swing/weekly horizon gamma analysis and explicitly excludes 0DTE, which helps with timing. However, it does not name sibling alternatives or explain when to choose this over related tools like get_daily_structure or get_gex_profile.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct metric or workflow—alert checks, alert lists, gamma maps, volatility indices, replay timelines, execution plans—so an agent can reliably pick the right one from its description. Even the alert-related tools (get_latest_alert, list_alert_history, check_alert_tradeable) have clearly separate outputs.
All tool names follow a consistent verb_noun snake_case pattern (mostly get_, plus check_, format_, list_, plan_). This makes the set predictable and easy to scan.
At 32 tools, the surface is heavy and approaches a disorganized collection of endpoints rather than a curated set. Many individual get_* indicators could be grouped into a smaller number of dashboard or snapshot tools without losing clarity.
The server covers the core 0DTE intelligence lifecycle: alerts, historical replays, risk overlays, structure, gamma, volatility, news, and advisory planning. Minor gaps exist—such as a direct quote or option chain feed—but they are not essential to the stated purpose.