SimianX AI

Points a call would cost, no execution

quote_post

Read-onlyIdempotent

Estimate how many points a SimianX call would cost before running it (pass the endpoint key, e.g. deep.create, and its options). Not a market price quote.

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": {
      "endpoint": "<endpoint>"
    },
    "name": "quote_post"
  }
}

Input Schema

Name	Required	Description
`asset`	No	stock \| crypto
`agents`	No	Subset of agents
`models`	No	agent -> model_id; omit to run on the account's saved setup (GET /v1/settings)
`endpoint`	Yes	Required: the endpoint key to price, e.g. analysis.quick, analysis.live, deep.create. This prices a SimianX call; it is not a market price quote

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 13, 2026

changedInput schema / properties / endpoint / description

Previous value: -"e.g. analysis.live, deep.create, autopilots.create"New value: +"Required: the endpoint key to price, e.g. analysis.quick, analysis.live, deep.create. This prices a SimianX call; it is not a market price quote"

changedInput schema / properties / models / description

Previous value: -"agent -> model_id (paid plans)"New value: +"agent -> model_id; omit to run on the account's saved setup (GET /v1/settings)"

removedInput schema / properties / tier

Removed value: -{
-  "description": "fast | standard | frontier",
-  "type": "string"
-}

addedInput schema / required
```
Added value: +[
+  "endpoint"
+]
```

First observedOct 16, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description reinforces the key behavioral point that nothing is executed, but says nothing about how the estimate is derived, whether it can fail for an unknown endpoint, or whether pricing reflects the supplied agents/models overrides.

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

Conciseness5/5

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

Two sentences, both earning their place: the first gives the action and its arguments, the second kills the dominant false interpretation. Front-loaded and free of filler.

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?

There is no output schema, but 'how many points ... would cost' effectively communicates the return value as a point quantity. For a four-parameter, non-destructive estimation tool this is nearly sufficient; only the behavior for invalid or unpriced endpoints is left unstated.

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 description, so the baseline applies. The description adds an endpoint example (deep.create) and the notion of passing 'its options', but largely restates what the schema documents more precisely.

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: estimate the point cost of a SimianX call without running it. The closing clause 'Not a market price quote' pre-empts the obvious misreading against quote-style siblings such as get_crypto_quotes, so an agent can route correctly without opening the schema.

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?

'before running it' makes the timing context explicit — this is a pre-flight check, not an execution path. It also tells the caller what to pass (endpoint key plus its options) and what it is not (a market quote), but it names no alternative tool for actually running the call.

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

All SimianX AI tools Inspect

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.