openrpc-mpc-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_callC | Call any JSON-RPC method on a server with parameters. A user would prompt: Call method on with params |
| rpc_discoverB | 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 is for executing arbitrary JSON-RPC methods, while rpc_discover is specifically for server discovery to list available methods. There is no overlap in functionality, making them easy to distinguish.
Both tools follow a consistent 'rpc_' prefix pattern with descriptive suffixes (call, discover), using snake_case throughout. This provides a predictable and readable naming convention across the tool set.
With only 2 tools, the server feels minimal but appropriate for its narrow scope of JSON-RPC interaction. However, it lacks tools for common operations like server health checks or parameter validation, which could enhance usability in this domain.
The tools cover the core actions of calling methods and discovering server capabilities, which aligns with the OpenRPC domain. However, there are notable gaps such as error handling tools, batch request support, or schema validation that would provide more comprehensive coverage for JSON-RPC workflows.