Skip to main content
Glama

Topology Index

by com.topologyindex
OverviewDiscussionsAdmin

List patterns

list_patterns
Read-onlyIdempotent

The decision guide: where to start by the shape of the task, the pattern to consider next and when to avoid each, plus the pattern families (the choosing rows of /patterns/index.md, without the rest of that page). With a family, /patterns/index.md?family={family}: that family’s patterns and the rows that name them. With a domain, /domains/{domain}.md: the task shapes common in that kind of work, their rows, the sources of the published findings tagged with it (never a ranking; each finding in words at /domains/{domain}/findings.md) and its starters. The response includes exact next calls for the listed patterns and starters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoRead the lens of one task domain instead; not together with a family.
familyNoRestrict the list to one pattern family.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nextYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "next": {
+      "items": {
+        "oneOf": [
+          {
+            "additionalProperties": false,
+            "properties": {
+              "arguments": {
+                "additionalProperties": false,
+                "properties": {
+                  "path_or_url": {
+                    "maxLength": 2048,
+                    "minLength": 1,
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "path_or_url"
+                ],
+                "type": "object"
+              },
+              "tool": {
+                "const": "fetch",
+                "type": "string"
+              }
+            },
+            "required": [
+              "tool",
+              "arguments"
+            ],
+            "type": "object"
+          },
+          {
+            "additionalProperties": false,
+            "properties": {
+              "arguments": {
+                "additionalProperties": false,
+                "properties": {
+                  "pattern": {
+                    "maxLength": 64,
+                    "minLength": 1,
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "pattern"
+                ],
+                "type": "object"
+              },
+              "tool": {
+                "const": "get_pattern",
+                "type": "string"
+              }
+            },
+            "required": [
+              "tool",
+              "arguments"
+            ],
+            "type": "object"
+          },
+          {
+            "additionalProperties": false,
+            "properties": {
+              "arguments": {
+                "additionalProperties": false,
+                "properties": {},
+                "type": "object"
+              },
+              "tool": {
+                "const": "list_patterns",
+                "type": "string"
+              }
+            },
+            "required": [
+              "tool",
+              "arguments"
+            ],
+            "type": "object"
+          }
+        ]
+      },
+      "maxItems": 32,
+      "type": "array"
+    }
+  },
+  "required": [
+    "next"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / domain
      Added value: +{
+  "description": "Read the lens of one task domain instead; not together with a family.",
+  "enum": [
+    "coding",
+    "research",
+    "documents",
+    "reasoning",
+    "evaluation",
+    "operations",
+    "security"
+  ],
+  "type": "string"
+}
  3. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, not open-world), and the description still adds real context: the domain findings are 'never a ranking,' findings are rendered 'in words,' and the response embeds exact next calls. That is meaningful behavior beyond the annotations, though it omits any pagination/size caveats.

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

Conciseness2/5

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

One long, colon-chained sentence-fragment block that mixes purpose, file paths, query-string syntax and return contents. It is information-dense but not front-loaded or skimmable; much of the path plumbing (/patterns/index.md?family={family}) crowds out the essential message.

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

Completeness4/5

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

With an output schema present, return values need not be explained, and the description still covers both optional parameters and the downstream routing. For a 2-param read-only listing tool this is nearly sufficient; only the missing sibling differentiation keeps it from being complete.

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% with both enums described, so baseline is 3. The description goes further by mapping each parameter choice to what it retrieves (a family yields that family's patterns and naming rows; a domain yields task shapes, tagged sources and starters), adding semantic value over the schema text.

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

Purpose3/5

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

The description frames the tool as a "decision guide" that returns pattern families, task shapes and next-step pointers, and it varies its output by the family/domain argument. However, it never states a clean verb+resource (e.g. "lists available patterns"), instead burying the purpose in path-level detail, so an agent must infer what is actually returned.

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

Usage Guidelines3/5

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

It explains what happens 'with a family' and 'with a domain,' which implies when to pass each, and it promises exact next calls, implicitly routing to get_pattern/fetch. But it never states when to prefer this over siblings like search, fetch, or list_starters, so comparison guidance is left to inference.

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

All Topology Index toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources