Returns a 0-100 Solana network health score plus the underlying metrics behind it. Useful before executing a timing-sensitive transaction. Paid: $0.002 per call via x402.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It does not explicitly state that the tool is read-only, safe, or has no side effects. While 'returns' implies a read operation, the agent lacks explicit confirmation of behavioral traits like idempotency or rate limits.
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 two sentences: one defining the return value, one providing use-case context and cost. Every sentence earns its place with no redundancy or fluff.
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?
Given the tool's simplicity (no parameters, no output schema), the description adequately covers what it returns and when to use it. However, it does not elaborate on the structure of 'underlying metrics' or any constraints (e.g., authentication, rate limits), which would improve completeness for an agent.
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?
There are zero parameters and schema description coverage is 100%, so the description does not need to add parameter meaning. The baseline of 4 is appropriate; no further elaboration is required.
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 clearly states the verb 'returns' and the resource 'Solana network health score plus underlying metrics'. It distinguishes itself from sibling tools (different blockchains, different purpose) by naming the specific blockchain and the health score focus.
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?
The description provides explicit guidance: 'Useful before executing a timing-sensitive transaction' and mentions cost ($0.002 via x402). It implicitly distinguishes from sibling tools (health checks for other chains, priority fee tools) but does not explicitly state when not to use or suggest alternatives.
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.
Each tool is clearly distinguished by its operation type (network health, priority fee, store, retrieve) and, where applicable, the specific blockchain (Base, Ethereum, Solana). No two tools perform the same function on the same target, so an agent can select the correct tool without ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case. The first six tools use 'get_' plus a descriptive noun (network_health or recommended_priority_fee) followed by the chain name, while the storage tools use 'store_' and 'retrieve_' with 'object'. This predictable convention aids agent selection.
With 8 tools, the server is well-scoped. The six network-related tools cover three blockchains across two recurring operations, and the two storage tools provide minimal yet sufficient coverage. The count is within the ideal range and each tool earns its place.
The network health and fee recommendation tools fully cover their immediate purposes. For object storage, only store and retrieve are provided, lacking delete or list operations. While the core workflow (write and read) is functional, the absence of delete is a minor gap that could require workarounds.