Courtship
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| discover_toolsB | Search available tools by keyword or intent without loading full schemas into context. |
| load_tool_schemaA | Load the full JSON schema for a specific tool into active context on-demand. |
| call_toolC | Invoke any tool through the proxy with automatic response compression and shaping. |
| love_taskC | Intelligent router for LÖVE development: routes to docs, live inspection, or code execution. |
| report_usageB | Returns the current session token ledger and savings breakdown. |
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 5 tools
The tools mostly occupy distinct roles: discovery, schema loading, proxied invocation, usage reporting, and a LÖVE-specific router. The only mild overlap is between love_task and call_tool, since both can lead to execution, but the descriptions make their intended levels of abstraction reasonably clear.
Four tools follow a clear verb_noun snake_case pattern: discover_tools, load_tool_schema, call_tool, report_usage. love_task deviates as a domain-specific noun phrase, but it remains readable and stylistically consistent in casing.
Five tools is well-scoped for a meta/proxy server focused on LÖVE development assistance. Each tool has a clear role in the discovery-to-invocation workflow, and there is no obvious padding.
The surface covers discovery, schema inspection, invocation, usage reporting, and a domain router, which is a coherent lifecycle for a proxy server. A dedicated list-all-tools operation is not explicit, though discover_tools likely covers most needs.