tessera-mcp
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_open_ticketsA | List support tickets currently in the 'open' state, worst priority first. Optionally filter by priority and cap the number returned. |
| get_customerA | Look up one customer by id or email and return their profile plus a summary of their invoices and tickets. Use this to investigate a specific account. |
| search_invoicesA | Search invoices with optional filters. Useful for spotting duplicate charges, overdue balances, or a customer's billing history. |
| daily_summaryA | A start-of-day operations snapshot: open tickets broken down by priority, count and dollar total of overdue invoices, and how many trials expire within 7 days. Takes no arguments. |
| update_ticket_statusA | Change a ticket's status (open, pending, or solved). Dry-run by default: returns a preview unless confirm:true is passed. |
| extend_trialA | Extend a trial customer's trial end date by a number of days. Only works for customers whose status is 'trial'. Dry-run by default: returns a preview unless confirm:true is passed. |
| issue_refundA | Refund a paid invoice. Fails if the invoice is not in 'paid' status (e.g. already refunded). Dry-run by default: returns a preview with the amount and customer unless confirm:true is passed. |
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 resource and action: tickets, customers, invoices, and trial management. No two tools overlap in purpose; daily_summary aggregates but does not duplicate list_open_tickets.
Most tools follow a clear verb_noun pattern (list_open_tickets, get_customer, update_ticket_status). The outlier is daily_summary, which uses a noun phrase rather than a verb, creating a minor inconsistency.
With 7 tools, the server is well-scoped for a support and billing domain. Each tool covers a distinct function without bloat or redundancy.
The tool set covers ticket status updates, customer lookups, invoice search, refunds, and trial extensions. Minor gaps exist, such as no way to list closed tickets or update customer details, but these are not essential to the core workflow.