andy
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_customizationsA | List all customization files (rules and skills) in the workspace and global directories. Args: workspace_path: Optional custom path to the workspace root. Default is CWD. |
| read_customizationA | Read the contents of a rule or skill file. Args: type: The customization type - either 'rule' or 'skill'. name: For 'rule', name is ignored or set to 'AGENTS.md'/.cursorrules. For 'skill', it's the skill folder name. workspace_path: Optional path to the workspace root. is_global: Set to True to read from global config, False to read from workspace. |
| write_proposalA | Write a learning_proposal.md file to the workspace root for user review. Args: content: The full markdown content of the proposal. workspace_path: Optional path to the workspace root. |
| apply_customizationA | Save the rules or skills customizations. Always ensure you have written a proposal and obtained user confirmation before calling this tool. Args: type: The customization type - either 'rule' or 'skill'. name: The name of the skill (required for skills). For rules, this can be empty or 'cursor'. content: The complete text content to write to the file. workspace_path: Optional path to the workspace root. is_global: Set to True to save globally, False to save to workspace. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| learn | Guides the agent through analyzing the chat history, drafting a proposal, and applying new rules/skills. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| read_workspace_rules | Read the active workspace rules (.cursorrules and .agents/AGENTS.md). |
| read_global_rules | Read the global rules (~/.gemini/config/AGENTS.md). |
| list_workspace_skills | List all workspace-specific skills and their summaries. |
| list_global_skills | List all global skills and their summaries. |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: apply_customization saves, list_customizations lists names, read_customization reads content, and write_proposal writes a separate proposal file. No two tools are ambiguous.
All tools follow a verb_noun pattern, but there is a minor pluralization inconsistency (list_customizations vs. singular other tools) and the noun changes from 'customization' to 'proposal'. Overall mostly consistent.
With 4 tools, the count is well-scoped for the domain of managing customizations and proposals. Each tool serves a necessary function without unnecessary duplication.
The toolset covers create/read/update for customizations but lacks a delete tool. Additionally, there is no tool to read or list proposals, only to write them. These gaps are notable but manageable.