Skip to main content
Glama

review_portfolio

Read-only treasury review: allocation buckets (cash, yield, tokens), top holdings, and optional drift vs target weights. Safe for cron — no proposals created.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "review_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetsNoOptional target allocation. Each row: { label, weightPercent, kind: cash|yield|token|symbol, symbol? }. Weights must sum to 100.
minLegUsdNoMinimum USD for rebalance legs (default 1)
driftThresholdPercentNoHysteresis band in percentage points (default 5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description must carry the safety profile, and it does: it declares read-only behavior and states explicitly that no proposals are created, which is the key mutability concern. It omits permissions, rate limits, and whether the review reflects live or cached data, so it is strong but not exhaustive.

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 compact sentences with the read-only guarantee front-loaded and the returned fields enumerated immediately after. Nothing is padded or repeated from the parameter schema.

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?

No output schema exists, so the description usefully summarizes the return payload (buckets, holdings, drift), and all three parameters are optional, keeping invocation risk low. The only gap is that drift and leg-sizing semantics are left entirely to the nested schema.

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 the baseline is 3. The description adds that targets are optional and that drift is computed against them, but it says nothing about minLegUsd or how driftThresholdPercent interacts with the drift output, leaving the schema to do that work.

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?

States a specific verb and resource ("Read-only treasury review") and enumerates exactly what it returns: allocation buckets across cash/yield/tokens, top holdings, and optional drift vs target weights. The closing "no proposals created" implicitly separates it from mutation siblings like plan_rebalance, but it does not name the sibling it contrasts with.

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?

"Safe for cron" and "optional drift vs target weights" imply the usage context (recurring monitoring, pass targets when you want drift analysis), but there is no explicit when-to-use / when-not-to-use statement and no named alternative such as plan_rebalance or get_portfolio. The routing is inferable rather than stated.

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