Trusteed Agentic Commerce

get_page_content

Read-onlyIdempotent

Get a SUMMARY of a specific page on Trusteed: its title, description, keywords, related tools and the link to the full page. It returns a summary, not the full page text: read the linked URL when the whole page is needed. content_scope says what came back. Pass the page slug (e.g. 'for-agents', 'pricing', 'blog') or a blog post slug (returns its excerpt). Use get_site_map first to discover available slugs. Pass page='blog' to list all blog posts.

Input Schema

Name	Required	Description	Default
`page`	Yes	Page slug (e.g. 'for-agents', 'pricing', 'trust') or blog post slug. Use 'blog' to list all blog posts.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

changedOutput schema / (root)

Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": true,
-  "properties": {
-    "category": {
-      "type": "string"
-    },
-    "content_scope": {
-      "enum": [
-        "summary",
-        "index"
-      ],
-      "type": "string"
-    },
-    "datePublished": {
-      "type": "string"
-    },
-    "description": {
-      "type": "string"
-    },
-    "excerpt": {
-      "type": "string"
-    },
-    "found": {
-      "type": "boolean"
-    },
-    "keywords": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "path": {
-      "type": "string"
-    },
-    "posts": {
-      "items": {
-        "additionalProperties": true,
-        "properties": {
-          "category": {
-            "type": "string"
-          },
-          "datePublished": {
-            "type": "string"
-          },
-          "excerpt": {
-            "type": "string"
-          },
-          "path": {
-            "type": "string"
-          },
-          "slug": {
-            "type": "string"
-          },
-          "title": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "slug",
-          "path",
-          "title",
-          "excerpt",
-          "category",
-          "datePublished"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "readingTime": {
-      "type": "string"
-    },
-    "related_tools": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "slug": {
-      "type": "string"
-    },
-    "suggestion": {
-      "type": "string"
-    },
-    "tags": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "title": {
-      "type": "string"
-    },
-    "total": {
-      "type": "number"
-    },
-    "type": {
-      "enum": [
-        "page",
-        "blog_post",
-        "blog_index"
-      ],
-      "type": "string"
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedSep 30, 2026

addedOutput schema / properties / content_scope

Added value: +{
+  "enum": [
+    "summary",
+    "index"
+  ],
+  "type": "string"
+}

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 / posts / 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: +{
+  "page": {
+    "description": "Page slug (e.g. 'for-agents', 'pricing', 'trust') or blog post slug. Use 'blog' to list all blog posts.",
+    "maxLength": 200,
+    "minLength": 1,
+    "type": "string"
+  }
+}

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

AddedJul 10, 2026

TDQS

A4.7/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, openWorld, non-destructive), so the bar is lower. The description adds genuinely useful behavior beyond them: it returns a summary rather than full text, `content_scope` indicates what came back, and a blog post slug yields only its excerpt. It does not describe pagination or error behavior, keeping it short of a 5.

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?

The summary-vs-full-text distinction is front-loaded, followed by the return contents, the scope caveat, and the slug/prerequisite guidance. Every sentence carries distinct information with no repetition.

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 no output schema, the description carries the return-shape burden and does so by listing the summary fields and the `content_scope` indicator. Prerequisite discovery and the blog-listing special case are both covered, so an agent has everything needed to call it correctly.

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% for the single `page` parameter, so the baseline is 3. The description adds value beyond the schema by giving concrete slug examples ('for-agents', 'pricing', 'blog') and noting that a blog post slug returns the post's excerpt, which clarifies accepted input forms.

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 (get) and resource (page content) and immediately scopes it: 'a SUMMARY ... not the full page text'. It enumerates what the summary contains (title, description, keywords, related tools, link), which cleanly separates it from siblings like get_site_map and search_docs.

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

Usage Guidelines5/5

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

Explicit routing: use get_site_map first to discover slugs, read the linked URL when the full page is needed, and pass page='blog' to list posts. It names the prerequisite tool and the fallback action rather than leaving them to inference.

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 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?