Canli Capital

Run tools

run_tool

Read-only

Run a tool find_tool named: one ({name, arguments}), or up to 25 ({calls: [...]}). Independent calls run concurrently; a failed call returns its own error and the rest still run. Read-only unless the paper-trading pack is on. Any argument can be {"$file": "path.csv", "column": "close"} (or "columns": [...] / "all") instead of pasted numbers. {"$result": i, "path": "close"} passes batch call i's output into a later call; every result also has a ref ("r1", ...) later calls pass the same way, {"$result": "r1", "path": "close"}, so data never needs copying.

Input Schema

Name	Required	Description
`name`	No	Tool name from find_tool (single call).
`view`	No	Draw the whole result for the person (charts, comparisons, option chains, yield curves, statements, backtest dashboards, order tickets) and return you a summary, where MCP Apps are drawn.
`calls`	No	Several calls in one round trip. Calls without $result references run concurrently.
`digits`	No	Round fractional numbers in the results to this many significant figures (4-6 saves output tokens); whole numbers such as counts, shares and IDs are never changed. Default: as each tool returns them.
`return`	No	For a batch: every result (default) or only the last one.
`select`	No	Return only these fields of each result, as dotted paths, e.g. ["verdict", "multiple_testing.best", "rows.0.accession"] (table rows take column names).
`receipt`	No	Add input and output SHA-256 and pack versions so the result can be recomputed and compared.
`arguments`	No	The tool's arguments (single call).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

addedInput schema / properties / view

Added value: +{
+  "description": "Draw the whole result for the person (charts, comparisons, option chains, yield curves, statements, backtest dashboards, order tickets) and return you a summary, where MCP Apps are drawn.",
+  "type": "boolean"
+}

First observedOct 15, 2026

TDQS

B3.4/5.0

Behavior1/5

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

Annotations declare readOnlyHint=true, but the description says 'Read-only unless the paper-trading pack is on,' which implies the tool may perform non-read-only operations under that pack. That directly conflicts with the unconditional readOnlyHint annotation, so the contradiction forces a 1 despite otherwise useful concurrency and failure-isolation details.

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?

It is compact and front-loads the core run-one/run-batch behavior with no filler. However, the first sentence is syntactically awkward and the final sentence packs multiple reference mechanisms together, slightly reducing readability.

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 complex proxy-runner with 8 parameters, an output schema, and annotations, it covers the critical execution semantics: single/batch, concurrency, error isolation, file/result substitution, and the read-only caveat. The main remaining gap is that the read-only exception is not reconciled with the annotation.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds important meaning beyond the schema by documenting the special $file and $result substitution syntax and result refs such as 'r1', which are not captured in the generic arguments 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 that it runs a tool discovered via find_tool, supporting either one call ({name, arguments}) or a batch of up to 25 ({calls: [...]}), which distinguishes it from the finder sibling. The phrasing 'Run a tool find_tool named' is awkward and it does not explicitly contrast with describe_tool, so it is clear but not perfect.

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?

It explains single vs. batch invocation, concurrent execution for independent calls, and failure isolation, and it points to find_tool as the source of the tool name. It does not explicitly state when to use this versus describe_tool or when a batch is preferable, so it gives clear context but no exclusions.

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

All Canli Capital 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.