Topology Index

Search Topology Index

search

Read-onlyIdempotent

Keyword search, with common synonyms, over pattern names, aliases and families, the decision guide, the domains, sources and benchmarks of published findings, research, starters and guides. At most 10 results, each a path for fetch; canonical pattern results also include the identifier for get_pattern and an exact next call. If no page matches every word, pages matching some; if none, the decision guide. Matches text only; never ranks patterns.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	Words to look for, such as "orchestrator worker", "verification" or "coding".

Output Schema

TableJSON Schema

Name	Required	Description	Default
`next`	No
`match`	Yes
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 2, 2026

addedOutput schema / properties / next

Added value: +{
+  "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"
+    }
+  ]
+}

addedOutput schema / properties / results / items / properties / next

Added value: +{
+  "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"
+    }
+  ]
+}

addedOutput schema / properties / results / items / properties / pattern
```
Added value: +{
+  "maxLength": 64,
+  "type": "string"
+}
```

changedOutput schema / properties / results / items / required

Previous value: -[
-  "path",
-  "url",
-  "title",
-  "snippet"
-]New value: +[
+  "path",
+  "url",
+  "title",
+  "snippet",
+  "next"
+]

Changed1 schema field changedSep 26, 2026

changedOutput schema / properties / match / enum

Previous value: -[
-  "all_words",
-  "any_word",
-  "none"
-]New value: +[
+  "all_words",
+  "any_word",
+  "none",
+  "empty"
+]

Changed3 schema fields changedSep 23, 2026

changedInput schema / properties / query / description

Previous value: -"Words to look for, such as \"orchestrator worker\" or \"debate\"."New value: +"Words to look for, such as \"orchestrator worker\", \"verification\" or \"coding\"."

addedOutput schema / properties / match

Added value: +{
+  "enum": [
+    "all_words",
+    "any_word",
+    "none"
+  ],
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "results"
-]New value: +[
+  "match",
+  "results"
+]

First observedSep 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses the result cap (at most 10), the fallback cascade (all-words match, then partial, then decision guide), and the matching semantics (text only, never ranks patterns). These are substantive behavioral traits the annotations do not cover.

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?

The scoping phrase is front-loaded and each sentence carries distinct information (coverage, result shape, fallback, matching). The long enumeration of searched surfaces is dense but earns its place; structure is efficient overall.

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?

With an output schema present and annotations covering the safety profile, the description supplies the remaining essentials: scope, result limit, result shape, and fallback behavior. Nothing an agent needs to call it correctly is missing.

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

Parameters3/5

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

There is a single query parameter with 100% schema description coverage, so the schema already carries the semantics. The description adds nothing about query syntax or length beyond the schema, making the baseline 3 appropriate.

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 (keyword search) and enumerates the resource surface it searches (pattern names, aliases, families, decision guide, domains, sources, benchmarks, research, starters, guides). An agent can immediately distinguish this from list_patterns/list_starters and understand it targets the topology index.

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

Usage Guidelines4/5

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

It routes the agent by explaining that each result is a path for `fetch` and that canonical pattern results carry the identifier for `get_pattern` plus an exact next call. That gives clear downstream context, but it never states when to prefer this over siblings like list_patterns or list_starters, so the exclusion guidance is implicit.

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

All Topology Index tools Inspect

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

Need Help?