quantifyme

Live Streaming Diagnostic

stream_test

Read-onlyIdempotent

Diagnostic: test whether LIVE data streaming works in this client.

Renders a widget with three panels — a JS timer (baseline), a WebSocket to
the live price feed, and an HTTP poll of /quote — each showing a live value
+ status, so you can see exactly which streaming mechanisms the client's
widget sandbox actually permits. Use when a live/ticking chart isn't moving.

Args:
  symbol: G7 pair to stream (default EURUSD).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`symbol`	No		EURUSD

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.1/5.0

Behavior4/5

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

Describes rendering a widget with three panels (JS timer, WebSocket, HTTP poll) each showing live value and status. Annotations already mark it as read-only, idempotent, and open-world. No contradictions.

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?

Front-loaded with key purpose, then explains widget details and usage in a few concise sentences. Every sentence adds value.

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 output schema present, no need to detail returns. For a diagnostic tool with one optional parameter, the description covers purpose, behavior, and usage adequately.

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 0%, so description carries full burden for parameter semantics. Only mentions 'G7 pair to stream (default EURUSD)' for the single param, adding marginal value. Sufficient for one param but not rich.

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?

Opens with 'Diagnostic: test whether LIVE data streaming works in this client,' specifying verb (test) and resource (streaming mechanisms). Clearly distinguishes from siblings like get_quote by being a diagnostic tool.

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?

Explicitly states 'Use when a live/ticking chart isn't moving,' providing clear when-to-use guidance. Does not mention when not to use, but context is sufficient.

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

All quantifyme 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

A3.9/5.0

Disambiguation4/5

Most tools have clearly distinct purposes, though browse_community, find_strategy, and one_shot (community_id) are related and could cause confusion if descriptions are not read carefully. Overall well-differentiated.

Naming Consistency4/5

Overwhelmingly follows a verb_noun pattern (browse_community, find_strategy, generate_strategy, get_deploy_result, etc.). A few exceptions like 'one_shot' and 'top_up' break the pattern but are still clear and memorable.

Tool Count4/5

13 tools cover the major functions of a trading strategy platform (discover, generate, deploy, monitor, account management). The count feels appropriate, though 'stream_test' is diagnotic and may not be needed in all contexts.

Completeness3/5

Covers core workflows well—browse, find, generate, deploy, and get results. However, lacks tools to update or stop a deployed model, and there's no way to edit an existing strategy, leaving some lifecycle gaps.

Resources

Need Help?