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

Name	Required	Description	Default
`query`	No	Words to look for, such as "orchestrator worker", "verification" or "coding". Only the first 200 characters are searched.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 2, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / query / description

Previous value: -"Words to look for, such as \"orchestrator worker\", \"verification\" or \"coding\"."New value: +"Words to look for, such as \"orchestrator worker\", \"verification\" or \"coding\". Only the first 200 characters are searched."

changedInput schema / properties / query / maxLength
```
Previous value: -200New value: +4096
```
removedInput schema / properties / query / minLength
```
Removed value: -1
```
removedInput schema / required
```
Removed value: -[
-  "query"
-]
```

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.6/5.0

Behavior5/5

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

Goes well past the readOnly/idempotent annotations by disclosing fallback behavior (all-words match, then partial match, then decision guide), the 10-result cap, and the semantic limit that it matches text only and never ranks patterns. These are behavioral traits an agent cannot infer from the annotations or schema.

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 purpose, then result shape, then fallback semantics; nearly every clause carries information. The middle sentence is densely packed with multiple ideas, but nothing is wasted.

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?

For a single-parameter search with an output schema and full annotation coverage, the description supplies everything additional an agent needs: scope of the index, synonym behavior, result cap, result-to-next-tool mapping, and degradation order. Nothing material 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% (including the 200-character search window), so the baseline is 3. The description adds real value by disclosing synonym expansion, which directly changes how an agent should phrase the query.

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 with synonym expansion) and enumerates the resource surfaces searched: pattern names, aliases, families, decision guide, domains, sources, benchmarks, research, starters, guides. This makes it clearly distinct from fetch, get_pattern, and list_patterns, which the description references by name.

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?

Explicitly routes the agent: each result is a path for `fetch`, canonical pattern results carry the identifier for `get_pattern` plus an exact next call. That is strong forward guidance, but it never states when NOT to use this tool (e.g., when to prefer list_patterns for browsing), so it sits just below the top mark.

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?