Skip to main content
Glama
Sign In

SimianX AI

by io.github.SimianX-AI
OverviewDiscussionsAdmin

Deprecated: use quick_read

run_live_analysis

Deprecated, sunset 2027-06-01: the same one-pass run as quick_read under its old name. Use quick_read. (uses points, metered on the models used like the website; deprecated (use /v1/analysis/quick))

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "asset": "<asset>",
      "symbol": "<symbol>"
    },
    "name": "run_live_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetYescrypto or stock (US stocks and ETFs)
agentsNoSubset of the four live agents (default all four)
modelsNoOnly when the user asks for specific models: agent -> model id from list_models (paid plans). Leave out to run on the user's saved setup (get_settings)
symbolYesStock ticker (NVDA) or coin (BTC); crypto also takes a pair id such as BTC-USDT-SWAP
languageNoLanguage of the write-ups, e.g. en, zh-CN, ja (default: the account's)
timeframeNoCandle timeframe. Crypto: 1m 5m 15m 1H 4H 1D. Stock: 1H 1D 1W 1mo. Default: the user's saved timeframe (get_settings)
idempotency_keyNoOptional: any unique string for this action; send the same one when retrying the same call and the first result comes back instead of the action running twice

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / idempotency_key
      Added value: +{
+  "description": "Optional: any unique string for this action; send the same one when retrying the same call and the first result comes back instead of the action running twice",
+  "maxLength": 128,
+  "type": "string"
+}
    • changedInput schema / properties / models / description
      Previous value: -"Per-agent model override, agent -> model id from list_models (paid plans)"New value: +"Only when the user asks for specific models: agent -> model id from list_models (paid plans). Leave out to run on the user's saved setup (get_settings)"
    • removedInput schema / properties / tier
      Removed value: -{
-  "description": "Model tier (default fast)",
-  "enum": [
-    "fast",
-    "standard",
-    "frontier"
-  ],
-  "type": "string"
-}
    • changedInput schema / properties / timeframe / description
      Previous value: -"Candle timeframe. Crypto: 1m 5m 15m 1H 4H 1D. Stock: 1m 15m 1H 1D 1W 1mo. Default 15m"New value: +"Candle timeframe. Crypto: 1m 5m 15m 1H 4H 1D. Stock: 1H 1D 1W 1mo. Default: the user's saved timeframe (get_settings)"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Adds real context beyond the annotations: the run consumes points and is metered by the models used, which the readOnlyHint=false / openWorldHint=true flags do not convey. It also discloses deprecation and the API path replacement (/v1/analysis/quick). Minor gap: no mention of latency or what the one-pass run returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The deprecation message is repeated three times in one sentence ('Deprecated, sunset...', 'old name', 'deprecated (use /v1/analysis/quick)'), and the nested parenthetical is hard to parse. It is short, but the redundancy and awkward nesting cost it.

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 deprecated 7-parameter alias, the definition covers what an agent needs: it is the same as quick_read, it costs points, and it is going away. No output schema exists, but the return value is inherited from the named replacement, so that is not a real gap.

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%, and each parameter already carries its own explanation (enums, defaults, idempotency semantics), so the description needs to do little. It adds nothing parameter-specific, which is acceptable at full coverage but earns only the baseline.

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?

States a specific verb and resource ('the same one-pass run as quick_read under its old name'), so the agent knows exactly what it does and that it is an alias of a named sibling. The deprecation status is front-loaded in the title and first words.

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?

Gives an explicit directive: 'Use quick_read,' which is the strongest possible when-not-to-use guidance. The sunset date (2027-06-01) adds a hard time boundary for choosing this tool.

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

All SimianX AI 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