Rabobank MCP Training Demo
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_customer_profileA | Retrieve a fake internal customer profile by customer ID. Example customer IDs: CUST-1001, CUST-2002. |
| get_product_infoA | Retrieve fake internal product information by product ID. Example product IDs: MORTGAGE-FLEX, PAYMENT-PLUS, BUSINESS-ACCOUNT. |
| get_api_endpoint_infoB | Retrieve API catalog information for an internal API. Example API names: customer-onboarding, product-catalog. |
| run_architecture_checkC | Run a fake internal architecture check for a service. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| api_security_review_prompt | Reusable review prompt for checking an API endpoint against internal standards. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| api_security_policy | Internal API security policy for demo purposes. |
| event_driven_standards | Internal event-driven architecture standards for demo purposes. |
TDQS
Scored across 4 tools
Each tool targets a distinct entity or action: customer profile, product info, API endpoint info, and architecture check. There is no overlap in purpose.
Three tools use the get_ prefix (get_customer_profile, get_product_info, get_api_endpoint_info), while one uses run_ (run_architecture_check). The pattern is mostly consistent but has a minor deviation.
With 4 tools, the server is well-scoped for a training demo. Each tool covers a different aspect, and the count is appropriate without being bloated or thin.
The tools cover the main read-only operations for a demo (customer, product, API info, and architecture check). Missing CRUD operations or additional resources like accounts/transactions could be considered gaps, but the demo purpose is adequately served.