Skip to main content
Glama

Ellimist

Index tracking with K assets

quantum_portfolio_index_tracking
Read-only

Use this to pick K assets and weights that track an index with minimal tracking error, from your own asset and index return series. Price: $0.05 USDC per call via x402 (no account). Not charged if it fails.

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": {
      "assets": "<assets>",
      "asset_returns": "<asset_returns>",
      "index_returns": "<index_returns>",
      "max_assets": "<max_assets>"
    },
    "name": "quantum_portfolio_index_tracking"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetsYes
backendNoaer
max_assetsYes
backend_noteNoset by Ellimist; leave empty
asset_returnsYesT x N
index_returnsYeslength T
requested_backendNoset by Ellimist; leave empty

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds pricing ($0.05 USDC per call via x402, no account required) and a failure-billing guarantee, which an agent cannot get from structured fields. It stops short of describing the result payload or how backend selection affects the computation.

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, no filler: the capability and its input framing come first, with the cost/billing caveat second. Every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a seven-parameter computational tool with no output schema, the description never says what comes back (weights plus K selected assets, and any tracking-error metric) or how the result should be interpreted. The billing details are handled well, but output expectations and backend semantics are missing.

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?

With 57% schema description coverage, the description usefully maps 'K assets' to max_assets and 'your own asset and index return series' to asset_returns/index_returns. It says nothing about backend, requested_backend, or backend_note, leaving three parameters undocumented in both places.

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 concrete verb and objective: select K assets and weights minimizing tracking error against an index. That is distinguishable from optimization/exposure siblings by its explicit tracking-error framing, though it never names an alternative to route against.

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?

'Use this to...' plus 'from your own asset and index return series' implies the prerequisite of supplying both return series, which is real guidance. However, there is no statement of when-not to use it or which sibling to pick for exposure, plain optimization, or risk questions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources