Skip to main content
Glama

Trust Page: publish

trust_page_publish
Idempotent

Publish (or replace) your company's public trust page: your claims with evidence fingerprints, plus the live health of your tamper-evident logs. Share the link in sales emails and security questionnaires. Requires the organization API key.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>",
      "headline": "<headline>",
      "claims": "<claims>"
    },
    "name": "trust_page_publish"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesShort web name for the page, e.g. acme-tooling
claimsYesWhat you want buyers to know, each {"label": "ISO 9001 certified", "document_sha256": "<64 hex>", "valid_until": "2027-06-30T00:00:00Z"}; fingerprint and date are optional
contactNoEmail or link for buyer questions
headlineYesOne sentence buyers read first

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, idempotent=true, destructive=false), it discloses two things the structured fields cannot: the page becomes publicly visible, and an organization API key is required. It also flags replace semantics, though it does not say what happens to existing claims or evidence when the page is replaced.

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?

Three tight sentences with the core action front-loaded and the requirement last. The middle sentence about sales emails is mildly promotional but still conveys a legitimate use case, so nothing is seriously wasted.

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?

For a 4-parameter, no-output-schema mutation tool, the description covers auth, idempotent replacement, and public exposure. The main residual gap is what the call returns (e.g., the published URL), which no output schema documents either.

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%, so the four parameters are already documented in the schema. The description only adds a light gloss on 'claims with evidence fingerprints' and does not add format or constraint detail beyond what the schema provides; baseline 3 applies.

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 and resource ('Publish (or replace) your company's public trust page') and clarifies the create-or-update semantics in parentheses. It is clearly distinguishable from a read-side tool like trust_page_view, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

It gives the downstream purpose ('Share the link in sales emails and security questionnaires') and a prerequisite ('Requires the organization API key'), which implies when to use it. However, there is no explicit when-not guidance or routing to trust_page_view for read-only inspection, so usage is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources