mcp-gateway

get_page_content

Read-onlyIdempotent

Read the content of a specific page on Trusteed. Pass the page slug (e.g. 'for-agents', 'pricing', 'blog') or a blog post slug. Use get_site_map first to discover available slugs. Pass page='blog' to list all blog posts.

Input Schema

TableJSON 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.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`path`	No
`slug`	No
`tags`	No
`type`	No
`found`	No
`posts`	No
`title`	No
`total`	No
`excerpt`	No
`category`	No
`keywords`	No
`suggestion`	No
`description`	No
`readingTime`	No
`datePublished`	No
`related_tools`	No

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

Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, and non-destructive behavior, so the bar for additional disclosure is lower. The description adds useful behavioral detail beyond the schema: the special semantics of page='blog' and the expectation that slugs come from get_site_map. It does not contradict annotations.

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?

Three short sentences with no filler. The core purpose is front-loaded, followed by parameter guidance and the prerequisite use of get_site_map. Every sentence earns its place.

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, read-only tool with rich annotations and an output schema, the description is complete. It tells the agent what slugs look like, how to discover them, and the special blog-listing behavior, so nothing essential is missing for correct invocation.

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 only one parameter and schema description coverage is 100%, so the schema already documents the page slug and the 'blog' special value. The description largely repeats the schema's parameter explanation rather than adding new semantic meaning, so the baseline of 3 is 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?

The description opens with a specific verb and resource: 'Read the content of a specific page on Trusteed.' It clearly distinguishes itself from siblings like get_site_map (which discovers slugs) and get_product_details (which returns product data), and adds the special 'blog' listing behavior.

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?

The description explicitly instructs to 'Use get_site_map first to discover available slugs,' which routes the agent to the correct precursor tool. It gives clear context for when this tool is appropriate, though it does not spell out explicit when-not-to-use exclusions against other siblings.

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?