mcp-gateway

search_docs

Read-onlyIdempotent

Full-text search across all Trusteed public documentation: pages, blog posts, and FAQ entries. Returns ranked results by relevance. Use this to find answers about protocols, pricing, integration guides, trust scores, and more.

Input Schema

TableJSON Schema

Name	Required	Description
`type`	No	Filter results by type: page, blog, or faq. Omit to search all types.
`limit`	No	Maximum number of results (1-20, default 10)
`query`	Yes	Search query, e.g. 'trust score threshold', 'shopify integration', 'rate limits'

Output Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes
`total`	Yes
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 17, 2026
- changedInput schema / additionalProperties
```
Previous value: -falseNew value: +true
```
- changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```
- changedOutput schema / properties / results / items / additionalProperties
```
Previous value: -falseNew value: +true
```
AddedSep 9, 2026
RemovedSep 1, 2026

Changed4 schema fields changedAug 24, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties

Added value: +{
+  "limit": {
+    "default": 10,
+    "description": "Maximum number of results (1-20, default 10)",
+    "maximum": 20,
+    "minimum": 1,
+    "type": "integer"
+  },
+  "query": {
+    "description": "Search query, e.g. 'trust score threshold', 'shopify integration', 'rate limits'",
+    "minLength": 2,
+    "type": "string"
+  },
+  "type": {
+    "description": "Filter results by type: page, blog, or faq. Omit to search all types.",
+    "enum": [
+      "page",
+      "blog",
+      "faq"
+    ],
+    "type": "string"
+  }
+}

addedInput schema / required
```
Added value: +[
+  "query"
+]
```

AddedJul 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds useful behavioral context: full-text search, coverage across documented types, relevance ranking, and the 'public' nature of the material.

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

Conciseness5/5

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

Two sentences, front-loaded with the core action and scope, followed by expected output and usage examples. No filler or redundancy.

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 simple read-only search tool with an output schema, 100% parameter coverage, and clear sibling separation, the description fully equips an agent to select and invoke it correctly.

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?

Schema description coverage is 100%, and the description does not need to add parameter details. It broadly aligns with the 'type' enum by mentioning pages, blog posts, and FAQ entries, but does not add meaning beyond 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 ('search') and a clear resource ('all Trusteed public documentation: pages, blog posts, and FAQ entries'), and names the result type ('ranked results by relevance'). This clearly distinguishes it from product-search siblings like search_products.

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?

Provides clear usage context ('Use this to find answers about protocols, pricing, integration guides, trust scores, and more') and the scope of what it searches. It does not explicitly name alternatives or exclusions, so it stops short of a full 5.

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

All mcp-gateway tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?