JSON-RPC
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XBY_APIKEY | Yes | 你的实际apikey (Your actual API key) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rpc_callB | Call any JSON-RPC method on a server with parameters. A user would prompt: Call method on with params |
| rpc_discoverC | This uses JSON-RPC to call |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: rpc_call executes specific JSON-RPC methods with parameters, while rpc_discover queries a server for available methods. There is no overlap in functionality, and an agent can easily differentiate between calling a method and discovering what methods exist.
Both tools follow a consistent snake_case naming pattern with the 'rpc_' prefix, clearly indicating their domain. The verbs 'call' and 'discover' are distinct and appropriate for their respective actions, maintaining a predictable structure throughout the set.
With only two tools, the server feels thin for a JSON-RPC domain, as it lacks operations like listing servers, handling authentication, or managing connections. While the tools cover basic calling and discovery, the count is borderline minimal for a server that could support more comprehensive RPC interactions.
The tool surface is significantly incomplete for a JSON-RPC server. It provides call and discovery but misses essential operations such as server management (e.g., add/remove servers), error handling, batch requests, or method documentation retrieval. This will likely cause agent failures when attempting more complex RPC workflows.