Capabilities
Tools, resources, prompts, and when to use each one
Capabilities
The MCP server exposes tools, resources, and one prompt.
Tools
| Tool | Use |
|---|---|
vrt_server_status | Check server status, upstreams, and auth state. |
vrt_product_help_search | Search product docs by literal text. |
vrt_team_lookup | Find accessible teams by name. |
vrt_api_read | Run GET requests against the VRPlatform API. |
vrt_api_mutation | Run POST, PATCH, PUT, or DELETE. |
Use vrt_product_help_search for product and operational guidance, not API
schema discovery. It is literal text search and rejects API-shape queries.
Resources
| Resource | Use |
|---|---|
vrt://service/info | Server metadata and environment summary. |
vrt://api/openapi-context | Compact API path and method catalog. |
vrt://api/path/%2Freservations | Path details for /reservations. |
vrt://api/path/%2Freservations/GET | Method parameters and response shape. |
Use OpenAPI resources for endpoint, parameter, schema, and response-field questions.
Path resources use URL-encoded paths. For example:
vrt://api/path/%2Fstatements
vrt://api/path/%2Fstatements/GETPrompts
| Prompt | Use |
|---|---|
vrt-trust-accounting-help | Starter prompt for accounting questions. |
Example Prompts
Use VRT MCP to find the team named Example PM and show its open issues.Read vrt://api/openapi-context, then inspect the GET shape for /reservations.
Summarize the available query filters.Using the configured team scope, call vrt_server_status and explain whether API
access is configured.