Skip to main content
Glama

veritas-8183-3star-rating-seal

get_trust_dossier_sample

Read-onlyIdempotent

View a fictional example of the full TrustGate dossier and its 0.25 USDC price on Base. The free preview includes all seven report sections and the delivered JSON structure.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_trust_dossier_sample"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, destructiveHint false, idempotent, closed-world), so the description only needs to add content-level context, which it does: the data is fictional, the preview is free, it contains seven sections, and it reflects the delivered JSON structure. It does not spell out pagination or exactly what the fictional payload contains, so it is not fully rich.

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 with no filler: the first establishes what is being viewed and the price, the second enumerates what the free preview contains. Nothing could be cut without losing signal.

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 zero-argument, read-only preview with no output schema and a 100%-covered schema, the definition covers the essentials: it clarifies that the data is fictional and that the response mirrors the paid deliverable's structure. A slightly fuller statement of the preview's shape would close the remaining gap.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate and it introduces no misleading parameter expectations.

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: it shows a fictional example of the full TrustGate dossier, and it flags the 0.25 USDC price on Base. The word 'example' signals this is sample data rather than a real audit, which separates it from the actual verification siblings; however, 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?

Implies the usage context by calling it a 'free preview' that includes all seven report sections and the delivered JSON structure, so an agent can infer it is for inspecting output before paying. There is no explicit when-to-use or when-not-to-use statement, and no prerequisite or follow-up action is named.

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.