DemoTool MCP Server
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| angular_component_standardsA | ⚠️ REQUIRED TOOL: Must be called before creating or modifying any Angular component. Returns Angular component standards and best practices to ensure code quality and consistency. Can retrieve all standards or filter by specific category. |
| data_fetching_standardsA | ⚠️ REQUIRED TOOL: Must be called before implementing data fetching or HTTP requests in Angular. Returns data fetching standards and best practices including rxResource, rxRequest, and HTTP patterns. Can retrieve all standards or filter by specific pattern. |
| design_system_standardsA | ⚠️ REQUIRED TOOL: Must be called before implementing design system components. Returns design system standards and best practices for buttons, cards, inputs, modals, and other components. Can retrieve all standards or filter by specific component. |
| design_system_available_componentsA | 📚 Component Registry: Returns comprehensive documentation for all design system components. Use this tool to discover available components (button, card, input, modal, etc.) and learn their APIs, props, events, examples, and usage patterns. Can retrieve all components or filter by specific component name. |
| angular_forms_standardsA | ⚠️ REQUIRED TOOL: Must be called before creating or modifying forms. Returns Angular forms standards and best practices for reactive forms, FormBuilder usage, and form validation. Can retrieve all standards or filter by specific category. |
| modal_best_practicesB | ⚠️ REQUIRED TOOL: Must be called before implementing modals or dialogs. Returns best practices for creating and managing modals/dialogs using DialogService, BaseDialogComponent, ds-modal components, and rxMethod patterns. Can retrieve all best practices or filter by specific category. |
| models_standardsA | ⚠️ REQUIRED TOOL: Must be called before creating or modifying models. Returns models standards and best practices for model development. Can retrieve all standards or filter by specific category. |
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 7 tools
Each tool targets a distinct Angular domain (components, data fetching, forms, models, modals, design system), so most selections are clear. There is mild overlap in the component cluster: design_system_standards explicitly covers modals while modal_best_practices is a separate tool, and design_system_available_components overlaps with design_system_standards.
Nearly all tools use snake_case with a <domain>_standards suffix (angular_component_standards, forms, models, design_system, data_fetching). The remaining two (design_system_available_components, modal_best_practices) deviate in suffix but stay readable and consistent in style.
Seven tools is well-scoped for a standards/reference server, with one tool per major Angular concern plus a component registry. No redundancy pushing the count up.
Covers the core Angular development concerns plus a component registry, giving solid coverage. Some common areas (routing, state management, testing, services/directives) are absent, but these are reasonable gaps for a standards-focused server.