Monitor recent transactions for any Solana address
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": {
"address": "<address>"
},
"name": "sol_whale_watch"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| address | Yes | Solana address to monitor |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states 'Monitor recent transactions' without explaining what 'monitor' entails (e.g., polling, streaming, one-time fetch), what 'recent' means, or what the output format is. Mutability, permissions, and rate limits are also not addressed.
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 sentence with no filler. It is appropriately sized and front-loaded with the action and resource.
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 tool with no output schema and no annotations, the description should explain what 'monitoring' returns or how it behaves over time. It lacks important context about expected results and use cases, especially given the existence of similarly named sibling tools.
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?
The input schema has one parameter 'address' described as 'Solana address to monitor', providing 100% coverage. The description adds no further semantic detail beyond this, so the baseline of 3 applies.
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 'Monitor recent transactions for any Solana address' has a specific verb (monitor) and resource (recent transactions for a Solana address). It is clear and unambiguous, but it does not distinguish this tool from siblings like sol_wallet_analysis, which likely also involves monitoring or analyzing wallet activity.
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 guidance is provided on when to use this tool versus alternatives. Sibling tools such as sol_wallet_analysis or sol_bridge_flows might serve overlapping purposes, but the description offers no context or exclusions.
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.