Scoped Support Tools Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DESCOPE_ISSUER | No | Expected JWT issuer. Defaults from DESCOPE_BASE_URL and DESCOPE_PROJECT_ID. | |
| DESCOPE_BASE_URL | No | Base Descope API URL. Defaults to https://api.descope.com. | |
| DESCOPE_JWKS_URI | No | JWKS URL used to verify token signatures. Defaults from DESCOPE_BASE_URL and DESCOPE_PROJECT_ID. | |
| DESCOPE_PROJECT_ID | No | Descope project ID used to build the default issuer and JWKS URL. Required for secure MCP server. | |
| DESCOPE_MCP_SERVER_ID | No | Expected JWT audience for this MCP server. Required for secure MCP server. |
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 |
|---|---|
| answer_user_queryB | Return a canned answer to a user's question. |
| process_refundB | Process a refund for a given order ID. |
| get_order_idA | Look up the order ID for a given customer ID. |
| lookup_customer_infoB | Return customer info for a given customer ID. |
| list_customersA | Return a list of all customers. |
| get_product_infoA | Return product info (name, price) for a product ID or name (e.g. 'macbook', 'iPhone'). |
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 6 tools
Each tool targets a distinct resource/action: customer lookup, listing, order ID retrieval, refund processing, product info, and a generic answer fallback. The only potential overlap is answer_user_query, but its purpose as a canned-response fallback is clear.
All tool names follow a consistent verb_noun snake_case pattern (e.g., process_refund, get_order_id, list_customers). No mixed conventions or unclear verbs.
With 6 tools, the server is well-scoped for a support-focused toolkit. The number is reasonable and each tool has a clear role without unnecessary redundancy.
Core support workflows are covered: customer lookup, product info, order ID retrieval, refund processing, and generic canned answers. Minor gaps exist (e.g., no order detail retrieval beyond ID), but these can be worked around with the existing tools.