Skip to main content
Glama

Trust Page: read a company's page

trust_page_view
Read-only

Read any company's Privi trust page: its claims, evidence fingerprints and whether its logs are intact right now. No organization key needed.

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>"
    },
    "name": "trust_page_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe page's web name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely new behavior: no organization key/authentication is required, and the response reflects current state ('whether its logs are intact right now'), meaning results are live rather than cached. It does not cover rate limits or pagination, but for a single-page read that is minor.

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 action and object, followed by the credential caveat. Every clause carries information; no filler or restatement of the title.

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?

With one required parameter, no output schema, and read-only annotations, the definition is close to complete: it says what the page returns and that no org key is needed. The remaining gap is the shape/format of the returned evidence fingerprints and log-integrity verdict, which an agent must discover at call time.

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 single 'slug' parameter is documented as 'The page's web name'. The description adds no format guidance, example, or slug-resolution behavior beyond the schema, so the baseline of 3 applies.

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 and resource ('Read any company's Privi trust page') and enumerates what the page contains (claims, evidence fingerprints, log integrity status). The read framing contrasts implicitly but clearly with the sibling trust_page_publish, so an agent can distinguish the two without inspecting schemas.

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?

The description implies a public, keyless lookup ('No organization key needed'), which tells the agent when this tool is callable without credentials. However, it never states when to prefer this over trust_page_publish or other trust/ledger tools, and gives no exclusions or preconditions beyond the missing key.

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