Plan a USD-valued portfolio rebalance from target mint percentages. targets[].bps must total 10000.
| Name | Required | Description | Default |
|---|---|---|---|
| owner | Yes | A Solana address in base58, 32-44 chars. | |
| targets | Yes | The desired portfolio: each mint and its share in basis points, summing to 10000. | |
| slippageBps | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description only mentions the bps sum constraint, but does not disclose side effects, auth needs, or what the plan output contains. Minimal behavioral disclosure.
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?
Extremely concise: one sentence plus a critical constraint. No wasted words.
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?
No output schema provided. Description does not mention return format or what the plan contains. For a planning tool, expected output is significant missing context.
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 covers 2 of 3 parameters (owner, targets) with descriptions. Description adds the bps total constraint, which is already in schema but reinforces. SlippageBps parameter lacks schema description and no additional explanation provided.
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?
Clearly states verb and resource: 'Plan a USD-valued portfolio rebalance'. Distinguishes from siblings like 'solknife_portfolio_compose_build' and 'solknife_portfolio_compose_execute' by being the planning step.
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?
No explicit guidance on when to use this over siblings or alternatives. Implicitly it's for planning, but lacks when-not-to-use or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.