ops-agent-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | Yes | Anthropic API key for the Claude model. | |
| OPS_AGENT_ALLOW_WRITES | No | If set to 'true', enables write operations on the MCP server. Defaults to false. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_ticketA | Open a support ticket for an account. WRITES DATA: only call when the user explicitly asked to create a ticket. [writes data] Arguments: {"account_id": {"description": "e.g. acc_002", "pattern": "^acc_[0-9]{3,6}$", "title": "Account Id", "type": "string"}, "subject": {"maxLength": 140, "minLength": 5, "title": "Subject", "type": "string"}, "priority": {"default": "medium", "enum": ["low", "medium", "high", "urgent"], "title": "Priority", "type": "string"}} |
| get_dealA | Get one deal by id, including its account and recent stage history. Arguments: {"deal_id": {"description": "e.g. deal_101", "pattern": "^deal_[0-9]{3,6}$", "title": "Deal Id", "type": "string"}} |
| list_dealsB | List deals, optionally filtered by pipeline stage, ordered by amount. Arguments: {"stage": {"anyOf": [{"enum": ["qualification", "proposal", "negotiation", "closed_won", "closed_lost"], "type": "string"}, {"type": "null"}], "default": null, "description": "Filter by pipeline stage", "title": "Stage"}, "limit": {"default": 10, "maximum": 25, "minimum": 1, "title": "Limit", "type": "integer"}} |
| list_open_ticketsA | List open support tickets, most urgent first. Optional priority filter. Arguments: {"priority": {"anyOf": [{"enum": ["low", "medium", "high", "urgent"], "type": "string"}, {"type": "null"}], "default": null, "description": "Filter by priority", "title": "Priority"}, "limit": {"default": 10, "maximum": 25, "minimum": 1, "title": "Limit", "type": "integer"}} |
| pipeline_summaryC | Aggregate deal count and BRL total per stage, plus open pipeline total. Arguments: {} |
| search_accountsA | Find customer accounts by (partial) name. Returns id, segment, city, owner. Arguments: {"query": {"description": "Account name fragment", "maxLength": 80, "minLength": 1, "title": "Query", "type": "string"}, "limit": {"default": 10, "maximum": 25, "minimum": 1, "title": "Limit", "type": "integer"}} |
| update_deal_stageA | Move a deal to another pipeline stage. WRITES DATA: only call when the user explicitly asked for the change and provided a reason. [writes data] Arguments: {"deal_id": {"pattern": "^deal_[0-9]{3,6}$", "title": "Deal Id", "type": "string"}, "stage": {"enum": ["qualification", "proposal", "negotiation", "closed_won", "closed_lost"], "title": "Stage", "type": "string"}, "reason": {"description": "Why the stage is changing (audited)", "maxLength": 280, "minLength": 5, "title": "Reason", "type": "string"}} |
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 have create/list, deals have get/list/update/pipeline summary, and accounts have search. There is no meaningful overlap that would cause an agent to select the wrong tool.
Most tool names follow a clear verb_noun pattern: create_ticket, get_deal, list_deals, list_open_tickets, search_accounts, update_deal_stage. The one deviation is pipeline_summary, which uses a noun phrase rather than an action verb, but the naming remains readable and predictable overall.
Seven tools is a well-scoped set for an ops agent handling accounts, deals, and support tickets. Each tool covers a necessary operation without redundancy or bloat.
The deal workflow is reasonably covered with list/get/stage updates and pipeline totals, but ticket support is incomplete: there is no way to fetch a single ticket, update it, or close/resolve it. Account coverage is also limited to search, with no account detail endpoint.