tw-market-data

List price alerts

list_alerts

Read-onlyIdempotent

Show the price-trigger rules you have armed, and whether each is still armed.

    A read-only inventory of thresholds you asked to be watched — it arms nothing and cancels
    nothing (`set_price_alert` arms, `delete_alert` cancels). Another customer's triggers are
    simply not visible here.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`hint`	No
`count`	No
`error`	No
`rules`	No
`reason`	No
`blocked`	No
`not_investment_advice`	No

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already mark the tool read-only, idempotent, and non-destructive, so the description's emphasis on 'arms nothing and cancels nothing' adds some redundancy but reinforces the safety profile. It adds genuinely useful behavioral context by stating that the results are scoped to the caller's own armed triggers and that another customer's triggers are not visible.

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?

The core statement is front-loaded and immediately understandable, with the additional side-effect and scoping details placed in a supporting sentence. It is slightly wordy with repetition of 'armed' and the metaphorical 'thresholds you asked to be watched,' but every major piece of information earns its place.

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

Completeness5/5

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

For a zero-parameter, read-only listing tool with rich annotations and an output schema available, this description is complete. It covers what is returned, the ownership scope, the armed-status information, and the relevant alternative tools, so an agent has enough context to call it correctly.

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?

The input schema has no properties, so there are no parameter semantics to document and schema coverage is complete by definition. The description still adds meaningful scope-level semantics by explaining that the returned inventory consists of thresholds the caller personally armed.

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: 'Show the price-trigger rules you have armed, and whether each is still armed.' It clearly identifies what is listed and the state information included, and it distinguishes itself from set_price_alert and delete_alert by naming them as the tools that perform those actions.

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

Usage Guidelines5/5

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

The description explicitly positions this as a read-only inventory and contrasts it with `set_price_alert` (arms) and `delete_alert` (cancels), making it clear when to use this tool versus those alternatives. It also clarifies that another customer's triggers are not visible, which helps an agent understand the scope and avoid expecting cross-account results.

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

All tw-market-data tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation4/5

The tools are largely distinct: querying, searching, backtesting, risk reads, alerts, memory, and audit functions each have clear homes. A few adjacent pairs (risk_read vs risk_assess, company_health_check vs positioning_read) could be confused, but the descriptions draw explicit boundaries.

Naming Consistency3/5

There are strong consistent clusters like list_*, get_*, run_*, and memory_*, but the *_read suffix alternates with noun-first names like company_health_check, and bare-verb tools like ask, calendar, chart, and screen break the pattern. The naming is readable but not uniform.

Tool Count2/5

Forty tools is well past the 25+ threshold and makes the surface heavy for an agent to navigate, even though the breadth reflects a genuinely wide platform. Several clusters could plausibly be consolidated without losing capability.

Completeness4/5

The tool surface covers the main lifecycle well: discovery, point-in-time querying, filings search and full text, backtesting, research, risk assessment, alerts, memory, approvals, and provenance verification. Minor gaps exist—no strategy management tools, no memory deletion, no bulk export—but agents can work around them.

Resources

Need Help?