intentplane
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_balanceA | Current balance of the account. [read-only, passed through by intentplane] |
| read_inboxC | The emails in the inbox. [read-only, passed through by intentplane] |
| send_moneyC | Send a transfer to an IBAN. [guarded by intentplane] |
| send_emailC | Send an email. [guarded by intentplane] |
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 targets a clearly distinct resource and action: account balance, inbox reading, money transfer, and email sending. There is no meaningful overlap between any pair.
All names follow a clean verb_noun pattern (get_balance, read_inbox, send_money, send_email). The minor get/read variation is natural and does not break predictability.
Four tools is a reasonable minimum for a small assistant-style server covering finance and email. It is slightly thin for the apparent breadth of those domains, but each tool earns its place.
Core read and send operations exist for both money and email, but there are notable gaps: no transaction history, no individual email retrieval/search, and no reply/delete operations. Agents can complete basic workflows but will hit dead ends for common follow-ups.