Fetches portfolio margin asset index prices by asset symbol, or returns all assets when no symbol is provided, for margin valuation and risk checks.
Query portfolio margin asset index price.
| Name | Required | Description | Default |
|---|---|---|---|
| asset | No | Asset symbol (e.g., BTC, ETH). If not provided, returns all assets | |
| recvWindow | No | The value cannot be greater than 60000 |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. "Query" implies a read-only operation, but the description does not mention authentication, rate limits, return behavior, or how recvWindow affects the request.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single front-loaded sentence with no redundant wording. It is appropriately concise for a simple query tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with two optional parameters and full schema coverage, the description is minimally adequate. However, with no annotations and no output schema, it should provide more context about behavior and expected results.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 input schema. The description adds no additional meaning about asset filtering or recvWindow beyond what the schema provides, making baseline 3 appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: "Query portfolio margin asset index price." It is clear what the tool returns, but it does not differentiate this tool from the many sibling portfolio-margin and market-data tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The agent must infer usage entirely from the tool name and one-sentence purpose.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.