Skip to main content
Glama
Zzero-net

Zero Network MCP Server

by Zzero-net

zero_api_reference

Access the Zero Network API reference to integrate gRPC endpoints for crypto payments, x402 paywalls, and MCP pricing. Retrieve documentation for Send, GetTransfer, GetHistory, GetBalance, GetAccount, BridgeIn, BridgeOut, and GetBridgeStatus.

Instructions

Get the Zero Network API reference — all 8 gRPC endpoints: Send, GetTransfer, GetHistory, GetBalance, GetAccount, BridgeIn, BridgeOut, GetBridgeStatus.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The `zero_api_reference` tool handler returns the `API_REFERENCE` string, which contains documentation for the 8 Zero Network gRPC endpoints.
    def zero_api_reference() -> str:
        """Get the Zero Network API reference — all 8 gRPC endpoints: Send, GetTransfer, GetHistory, GetBalance, GetAccount, BridgeIn, BridgeOut, GetBridgeStatus."""
        return API_REFERENCE
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states what the tool returns (API reference with 8 endpoints) but lacks behavioral details like response format, data freshness, rate limits, authentication needs, or error handling. The description is functional but minimal on behavioral context.

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

Conciseness5/5

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

The description is a single, efficient sentence that front-loads the purpose ('Get the Zero Network API reference') and provides specific details (8 gRPC endpoints listed). There is zero wasted text, making it highly concise and well-structured.

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

Completeness4/5

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

Given the tool's simplicity (0 parameters, output schema exists), the description is reasonably complete. It specifies the content (API reference with 8 endpoints) without needing to explain return values due to the output schema. However, it could benefit from more behavioral context given the lack of annotations.

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

Parameters4/5

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

The tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description appropriately omits parameter details, focusing on the tool's output. Baseline is 4 for zero-parameter tools when schema coverage is complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Get') and resource ('Zero Network API reference'), listing all 8 gRPC endpoints by name. It distinguishes itself from siblings like zero_overview or zero_network_parameters by focusing on API endpoints rather than general information or parameters.

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

Usage Guidelines3/5

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

The description implies usage when needing API endpoint details, but provides no explicit guidance on when to choose this tool over alternatives like zero_implementation_guide or zero_javascript_sdk. No exclusions or prerequisites are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Zzero-net/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server