temp-notes
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 |
|---|---|
| clear_noteB | Clears the current note, making it empty. |
| write_noteC | Replaces the current note with a new string. |
| read_noteB | Returns the current content of the note. |
| append_noteA | Appends new text to the current note, starting with a new line. Optionally includes a separator line. |
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 4 tools
Each tool has a clearly distinct purpose: append_note adds to the note, clear_note empties it, read_note retrieves content, and write_note replaces it. There is no overlap or ambiguity between these operations.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., append_note, clear_note). The naming is predictable and uniform throughout the set.
With 4 tools, this server is well-scoped for managing a single note. Each tool serves a distinct and necessary function, making the count appropriate for the domain.
The tool set provides complete CRUD-like coverage for a note-taking domain: create/replace (write_note), read (read_note), update (append_note), and delete (clear_note). There are no obvious gaps for the intended purpose.