MCP-Server-Inbox
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INBOX_USER_TOKEN | Yes | Your inBox API token or complete URL (e.g., your_user_token_here or @https://inbox.gudong.site/api/inbox/your_token_here) |
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 |
|---|---|
| write_noteC | Write note to inBox |
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 1 tool
With only one tool, there is no possibility of confusion or overlap between tools, making disambiguation perfect. The tool's purpose is singular and clearly defined as writing notes to an inbox.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'write_note' follows a clear verb_noun pattern, and there are no other tools to compare or create inconsistency with.
A single tool is too few for a server named 'MCP-Server-Inbox', which suggests a domain involving inbox management. This minimal toolset likely leaves significant gaps in functionality, such as reading, updating, or deleting notes, making it inappropriate for the implied scope.
The tool surface is severely incomplete for an inbox server. It only provides a 'write_note' tool, lacking essential operations like reading notes, listing notes, updating notes, deleting notes, or managing inbox states, which will cause agent failures in handling inbox workflows.