Skip to main content
Glama
Sign In

SimianX AI

by io.github.SimianX-AI
OverviewDiscussionsAdmin

Deprecated: use get_quick_read

get_live_analysis
Read-onlyIdempotent

Deprecated, sunset 2027-06-01: status and results of a run started with run_live_analysis. Use get_quick_read. (deprecated (use /v1/analysis/quick/{id}))

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": {
      "run_id": "<run_id>"
    },
    "name": "get_live_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoSeconds to wait for the run to finish, 0-25 (default 0)
run_idYesRun id from run_live_analysis
includeNotext: include each agent's full write-up

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Read-only, idempotent, and non-destructive behavior is already declared by annotations, and the annotation title already flags deprecation, so the description's main addition is the concrete sunset date and the replacement endpoint. It does not explain what happens when the wait window expires (partial results vs. error) or whether polling is expected, which is the meaningful behavioral gap for this kind of run-status tool.

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 deprecation and migration path are front-loaded in a single efficient sentence. The trailing parenthetical '(deprecated (use /v1/analysis/quick/{id}))' repeats information already given and is the only wasted verbiage.

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, zero-output-schema retrieval tool, the definition supplies everything an agent needs to make the routing decision: replacement tool, replacement endpoint path, sunset date, and what the call returns. Only the wait/timeout response semantics are left implicit.

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%, so run_id, wait (0-25 seconds), and include=text are all already documented in the schema. The description adds only that run_id comes from run_live_analysis, which is minimal but consistent with a well-documented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it returns 'status and results of a run started with run_live_analysis', which pins down both the object and the origin of the required run_id. It is distinguishable from siblings, though the deprecation notice and the alternate endpoint phrasing compete slightly with the core purpose statement.

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?

It names the explicit alternative (get_quick_read) and the exact sunset date, so an agent knows both when not to use this tool and when it will stop working entirely. There is no ambiguity about the recommended path.

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