Skip to main content
Glama

List systemic patterns

list_systemic_patterns
Read-only

List the SYSTEMIC PATTERNS the platform tracks: issues that have recurred AND been remediated repeatedly, grouped by whoever can fix them at source. ALWAYS call this before diagnosing a recurring problem, and whenever the user asks why something keeps happening, keeps coming back, or has happened before. Each entry carries occurrence / distinct-cluster / distinct-day counts, how many times an agent remediated it, and an interpretation field stating what the row means for your answer - read that field before replying. A pattern with status 'escalated' has ALREADY been reported for a permanent fix (to the Ankra platform team as a support ticket, or to a stack profile's owner as a change request): say so and cite escalation_reference instead of re-diagnosing, and never report it again. Scope 'platform' means the defect arrives with every cluster Ankra provisions; 'stack_profile' means one profile version ships it to every deployment of that profile; 'local' is confined to one cluster and is never reported upstream. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cluster_id": "<cluster_id>"
    },
    "name": "list_systemic_patterns"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum patterns to return (default 10, max 50).
scopeNoOptional scope filter.
statusNoOptional lifecycle filter; 'escalated' lists what has already been reported for a permanent fix.
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
this_cluster_onlyNoRestrict to patterns concerning the selected cluster - its own local pattern plus the platform and stack-profile patterns it contributed occurrences to. Ignored when no cluster is selected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare readOnlyHint, so the description carries the burden and does: it explains the escalated lifecycle state, instructs the agent to cite escalation_reference rather than re-diagnose, warns never to report it again, and names the interpretation field that must be read before replying. It also discloses the upstream-reporting boundary of each scope.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the definition, then usage triggers, then behaviour, then scope semantics — a sensible order with no filler sentences. It is a dense wall of prose, though, and the scope semantics and escalated behaviour would be easier to scan as separate clauses or bullets.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, yet the description enumerates the returned fields (occurrence, distinct-cluster, distinct-day counts, remediation count, interpretation) and tells the agent how to use them. For a read-only list tool with fully documented params, nothing an agent needs before calling or interpreting results is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns above that by giving the scope enum real semantics ('platform' means the defect arrives with every provisioned cluster, 'stack_profile' means one profile version ships it everywhere, 'local' is never reported upstream) and by reinforcing what the 'escalated' status filter returns. It adds nothing for limit, cluster_id, or this_cluster_only, but those are fully documented in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource and defines the resource precisely: issues that have recurred AND been remediated repeatedly, grouped by who can fix them at source. That definition distinguishes it from adjacent tools like list_security_findings or list_security_finding_occurrences, which also deal with recurring issues.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit imperative trigger ('ALWAYS call this before diagnosing a recurring problem') plus natural-language conditions ('why something keeps happening, keeps coming back, or has happened before'). It also implies the alternative behaviour it should replace: re-diagnosing a problem that is already escalated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.