Finance MCP

Run a finance tool

finance_run

Execute a finance tool by id with params. Each successful run costs credits from the account balance (see costCredits in finance_inspect); failed runs are not charged. Failed vendor calls return an error.

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": {
      "id": "<id>",
      "params": "<params>"
    },
    "name": "finance_run"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Tool id from finance_discover, e.g. okx#ticker
`params`	Yes	Tool input params (see finance_inspect)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that successful runs cost credits, failed runs are not charged, and failed vendor calls return an error. However, it omits auth requirements, side effects, idempotency, and return shape, which are significant for an execution tool.

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?

The description is three short sentences with zero waste. It front-loads the action and then layers in cost and failure behavior efficiently.

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 two-parameter tool with full schema coverage, the description adds the key operational facts: credit cost and failure charging behavior. It remains slightly incomplete because there is no output schema and the description does not explain the return value or error shape, but it is otherwise sufficient to call the tool correctly.

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 both parameters are already documented in the schema, including the id example and params reference to finance_inspect. The description only restates that the tool takes an id and params, so it adds no meaning beyond the schema baseline.

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 uses a specific verb and resource: it executes a finance tool by id with params. It clearly distinguishes the core action from finance_discover and finance_inspect, though only finance_inspect is explicitly referenced for cost details. The purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies that the id comes from finance_discover and params from finance_inspect via the schema, but it does not explicitly state when to call this versus the sibling discovery/inspection tools. It mentions finance_inspect only for costCredits, which is helpful but not full usage guidance.

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

All Finance MCP 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.