Skip to main content
Glama

Trusteed Agentic Commerce

by xyz.trusteed
OverviewDiscussionsAdmin

search_docs

Read-onlyIdempotent

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

Input Schema

NameRequiredDescriptionDefault
typeNoFilter results by type: page, blog, faq, error (error codes), guide (checkout guide sections) or tool (tools served by this endpoint). Omit to search all types.
limitNoMaximum number of results (1-20, default 10)
queryYesSearch query, e.g. 'trust score threshold', 'shopify integration', 'rate limits'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": true,
-  "properties": {
-    "query": {
-      "type": "string"
-    },
-    "results": {
-      "items": {
-        "additionalProperties": true,
-        "properties": {
-          "excerpt": {
-            "type": "string"
-          },
-          "path": {
-            "type": "string"
-          },
-          "score": {
-            "type": "number"
-          },
-          "slug": {
-            "type": "string"
-          },
-          "title": {
-            "type": "string"
-          },
-          "type": {
-            "enum": [
-              "page",
-              "blog",
-              "faq",
-              "error",
-              "guide",
-              "tool"
-            ],
-            "type": "string"
-          }
-        },
-        "required": [
-          "type",
-          "slug",
-          "path",
-          "title",
-          "excerpt",
-          "score"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "total": {
-      "type": "number"
-    }
-  },
-  "required": [
-    "results",
-    "total",
-    "query"
-  ],
-  "type": "object"
-}New value: +null
  2. Changed3 schema fields changed
    • changedInput schema / properties / type / description
      Previous value: -"Filter results by type: page, blog, or faq. Omit to search all types."New value: +"Filter results by type: page, blog, faq, error (error codes), guide (checkout guide sections) or tool (tools served by this endpoint). Omit to search all types."
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "page",
-  "blog",
-  "faq"
-]New value: +[
+  "page",
+  "blog",
+  "faq",
+  "error",
+  "guide",
+  "tool"
+]
    • changedOutput schema / properties / results / items / properties / type / enum
      Previous value: -[
-  "page",
-  "blog",
-  "faq"
-]New value: +[
+  "page",
+  "blog",
+  "faq",
+  "error",
+  "guide",
+  "tool"
+]
  3. Changed1 schema field changed
    • addedInput schema / properties / query / maxLength
      Added value: +200
  4. Changed3 schema fields changed
    • 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
  5. Added
  6. Removed
  7. Changed4 schema fields changed
    • 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"
+]
  8. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds value beyond that by stating results are ranked by relevance and by scoping the searchable corpus, though it omits any note on pagination or result truncation.

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?

Purpose is front-loaded in the first clause with the corpus list following, then return behavior, then usage. Efficient, though the final sentence's content areas partly restate the first sentence's enumeration.

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?

No output schema exists, so the description must convey return behavior, which it does ('ranked results by relevance'). Combined with fully documented parameters and rich annotations, it is nearly complete for a simple search tool; only pagination/result-count semantics are unstated.

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% (type enum, limit bounds, query examples all documented inline), so the baseline is 3. The description's enumeration of content types loosely maps to the type filter but adds no syntax or format detail beyond what the schema already carries.

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

Purpose4/5

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

States a specific verb (full-text search) and resource (Trusteed public documentation) and enumerates the covered content types. An agent can distinguish this from get_page_content (fetches a single page) and search_products (product search), though it never names those siblings explicitly.

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?

"Use this to find answers about protocols, pricing, integration guides, trust scores, and more" gives clear context for when to reach for the tool. It stops short of naming alternatives or stating when-not to use it, so no explicit routing guidance.

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

All Trusteed Agentic Commerce toolsInspect
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