Enterprise MCP Template
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| healthA | Health check for the MCP server. Returns server status, configuration validity, and version information. |
| pingA | Simple ping/pong health check. Returns 'pong' if the server is responsive. |
| create_recordC | Create a new record in the upstream API. TEMPLATE: Replace this docstring with your domain-specific documentation. The docstring is shown to AI clients to help them understand when and how to use this tool. Args: record_type: The type of record to create (e.g., "customer", "invoice") payload: JSON payload for the record. account_id: Account ID (required if not configured on server). base_url: Optional full API URL (overrides account_id). Returns: Structured response with ok, status_code, data, errors, request_id. |
| get_recordA | Fetch a record from the upstream API by ID. Args: record_type: The type of record (e.g., "customer", "invoice") record_id: Internal ID of the record. account_id: Account ID (required if not configured on server). base_url: Optional full API URL (overrides account_id). expand_sub_resources: Include full sublist/related data. Returns: Structured response with record data. |
| update_recordB | Update an existing record in the upstream API. Args: record_type: The type of record (e.g., "customer", "invoice") record_id: Internal ID of the record. updates: Dictionary of fields to update. account_id: Account ID (required if not configured on server). base_url: Optional full API URL (overrides account_id). Returns: Structured response with update result. |
| delete_recordA | Delete a record from the upstream API. Args: record_type: The type of record (e.g., "customer", "invoice") record_id: Internal ID of the record. account_id: Account ID (required if not configured on server). base_url: Optional full API URL (overrides account_id). Returns: Structured response with deletion result. |
| execute_queryC | Execute a query against the upstream API. TEMPLATE: Replace with your API's query language documentation. Examples: SuiteQL (NetSuite), SOQL (Salesforce), GraphQL, OData, etc. Args: query: Query string in the upstream API's query language. account_id: Account ID (required if not configured on server). base_url: Optional full API URL (overrides account_id). limit: Maximum number of results. offset: Starting offset for pagination. Returns: Structured response with query results. |
| get_record_schemaC | Get the schema/structure for record payloads. Returns documentation about expected payload formats. TEMPLATE: Replace with your domain-specific schema documentation. This helps AI clients construct correct payloads. |
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 8 tools
Every tool has a clearly distinct purpose with no ambiguity. The CRUD operations (create_record, get_record, update_record, delete_record) are well-separated from query execution (execute_query), schema retrieval (get_record_schema), and health checks (health, ping). The descriptions clearly differentiate each tool's function, making misselection unlikely.
All tool names follow a consistent verb_noun pattern with snake_case throughout. The naming is predictable and readable, with verbs like create, delete, execute, get, and update paired with appropriate nouns like record, query, schema, or simple actions like ping/health.
The 8 tools are well-scoped for an enterprise API template server. This includes complete CRUD operations, query execution, schema retrieval, and health checks, which is appropriate for interfacing with various upstream APIs. Each tool earns its place without feeling excessive or insufficient.
The tool surface provides complete CRUD/lifecycle coverage for record management (create, get, update, delete), plus essential utilities like query execution, schema documentation, and health checks. There are no obvious gaps for the server's purpose of interacting with enterprise APIs, and agents can perform all expected operations without dead ends.