CryptoBoss

get_portfolio_health

Portfolio diversification: concentration, correlation, sector exposure. $0.02.

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": {
      "api_key": "<api_key>",
      "holdings": "<holdings>"
    },
    "name": "get_portfolio_health"
  }
}

Input Schema

Name	Required	Description	Default
`api_key`	Yes
`holdings`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 11, 2026

TDQS

C2.6/5.0

Behavior3/5

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

The description mentions a $0.02 cost per call, which is a key behavioral trait. However, with no annotations, it fails to disclose if the tool is read-only, any side effects, rate limits, or data freshness. The cost information adds value but leaves significant gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short (two fragments and a cost note). While concise, it sacrifices essential information. It could be more structured but avoids verbosity.

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

Completeness1/5

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

Given no output schema, no annotations, and low schema coverage, the description is severely incomplete. It does not explain return format, how to interpret results, or provide examples. The tool's behavior remains largely opaque.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description does not explain the 'api_key' or 'holdings' parameters. The meaning of 'holdings' (e.g., JSON format, list of tickers) is completely absent, leaving the agent uninformed.

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 specifies the tool assesses portfolio diversification metrics (concentration, correlation, sector exposure), which clearly indicates its purpose. It distinguishes from siblings like get_portfolio_value and get_price by focusing on health rather than value or price.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., get_portfolio_value, market_correlation). No prerequisites or context about required holdings format or input preparation are provided.

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

All CryptoBoss 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?