embrace-raw-readonly
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EMBRACE_API_TOKEN | Yes | Service-account token used for authenticating with the Embrace API. Must be inherited by the MCP client process. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| embrace_list_readonly_toolsA | Return the official Embrace read-only tool schemas as full JSON. |
| embrace_call_readonlyA | Call one published Embrace tool and return its complete JSON-RPC result. This intentionally accepts arbitrary JSON arguments because the remote tool schemas evolve independently. Use embrace_list_readonly_tools first when the required arguments are unknown. |
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: one lists available tools, the other invokes a specific tool. There is no overlap or ambiguity in selecting between them.
Both tools start with 'embrace_' and include 'readonly', but one is 'list_readonly_tools' (verb_noun) while the other is 'call_readonly' (verb_adjective). The pattern is mostly consistent but not perfectly parallel.
With only two tools, the surface is thin. However, this is a deliberate thin proxy layer for a remote readonly API, so the minimalism is justified, but it still falls below the typical well-scoped range.
The two tools form a complete interface for interacting with the remote readonly toolset: listing available schemas and calling them. There are no missing operations within the stated scope of acting as a proxy.