Analyzera

List rebalance targets

list_rebalance_targets

Read-onlyIdempotent

The target weights pre-rebalance notices have sent for a strategy, latest first, each labelled with its rebalance date. portfolio_id is a strategy, or an account, which reads the strategy it tracks (list_portfolios shows which). Weights only; none is readable before its 12:00 Stockholm release.

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": {
      "portfolio_id": "<portfolio_id>"
    },
    "name": "list_rebalance_targets"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`portfolio_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare the safe read-only, idempotent, closed-world profile, and the description adds real behavior on top: latest-first ordering, the 12:00 Stockholm release gate that makes recent notices unreadable, weights-only payload, and the account-to-strategy resolution. These are traits an agent could not infer from structured fields.

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?

Three dense sentences with no filler, and the resource definition is front-loaded before the ID and embargo notes. The opening clause ('The target weights pre-rebalance notices have sent') is grammatically compressed enough to cost a re-read, keeping it just under top marks.

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?

An output schema exists so return values needn't be described, and the description covers the ID's polymorphic nature and the temporal gate. The one gap is the 'limit' parameter's effect, which is left entirely to the schema's default/min/max constraints.

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 0%, so the description carries the burden. It handles portfolio_id well (strategy or account, tracking resolution), but never mentions 'limit' – that it caps the number of notices returned, has default 3, and maxes at 12. Half of the parameter semantics are left to inference.

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 precise verb and resource: it returns target weights from pre-rebalance notices for a strategy, ordered latest first and labelled with the rebalance date. The reader knows exactly what comes back and how it differs from list_portfolios or the weight describe tools.

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?

Explains the key precondition for the required id ('portfolio_id is a strategy, or an account, which reads the strategy it tracks') and routes to list_portfolios to resolve that mapping. It also flags the 12:00 Stockholm release embargo. What's missing is any explicit statement of when to use this over siblings such as describe_portfolio_weights.

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

All Analyzera 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.

Resources

Need Help?