agent-ops-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_tasksA | List tasks from the team tracker, optionally filtered by status or assignee. |
| get_taskB | Get a single task by id. |
| create_taskC | Create a new task in the tracker. |
| search_docsA | Full-text search over the internal docs/wiki (style guide, runbooks, checklists). Stands in for hitting a real Confluence-style docs API. |
| get_docA | Fetch the full content of a doc by id (from search_docs results). |
| review_checkA | Run heuristic checks (secrets, leftover TODOs, placeholder text, size) over generated text or a diff before it goes to a human reviewer — mirrors the team's pre-review checklist doc. |
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 and action: tasks (list/get/create), docs (search/get), and a review check. There is no overlap or ambiguity between them. An agent can easily select the right tool for each intent.
All tool names follow a consistent snake_case verb_noun pattern (list_tasks, get_doc, review_check). The verbs are clear and the style is uniform throughout. This makes the API predictable and easy to extend.
With only 6 tools, the surface is well-scoped and focused. Each tool earns its place by covering a necessary operation without bloat. This is an ideal size for an agent helper that combines tasks, docs, and quality checks.
Task management is incomplete: you can create and list tasks but cannot update, delete, or change status, which are common operations. Docs are read-only (search/get), which is acceptable for a reference. Adding update/delete for tasks would round out the lifecycle.