Skip to main content
Glama

veritas-8183-3star-rating-seal

inspect_veritas_8183_seal

Read-onlyIdempotent

[Public registry] Before trusting a seller: see its 1-3 star seal, reserve ratio, trust history and whether risky actions would be blocked. Free. Example: targetId='ALL'. Call with {} for a free read-only sample preview.

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": "inspect_veritas_8183_seal"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetIdNoStore ID, agent ID, or 'ALL' for the full directory.
roleFilterNoFilter directory output by SELLER or BUYER.
callerSectorOrTrendNoSingle industry sector or keyword to query radar search intelligence.
forensicUnlockTokenNoSingle-use unlock token issued by manage_buyer_finops_spend_passport.
buyerIdForSimulationNoBuyer agent ID for bilateral pre-check or single-use unlock.
preExecutionCallCheckNoOptional tool call payload to evaluate in the pre-execution firewall.
simulatedUpdateBehaviorNoOptional update payload to evaluate version drift before deployment.
versionToInspectOrUpdateNoAgent version string to inspect for behavioral drift (v1 vs v2).
proposedTransactionAmountUsdcNoOptional USDC amount to check against buyer FinOps spend caps.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / required
      Added value: +[]
  2. Changed10 schema fields changed
    • changedInput schema / properties / buyerIdForSimulation / description
      Previous value: -"Optional buyer agent ID for bilateral pre-check."New value: +"Buyer agent ID for bilateral pre-check or single-use unlock."
    • changedInput schema / properties / callerSectorOrTrend / description
      Previous value: -"Optional: specify ONE (1) single industry sector or keyword query to unlock WHO searched, HOW MANY TIMES, and with WHICH EXACT KEYWORDS (requires 1-time registration trial or 0.25 USDC per sector)."New value: +"Single industry sector or keyword to query radar search intelligence."
    • changedInput schema / properties / forensicUnlockToken / description
      Previous value: -"Optional 1-Time Single-Use Unlock Token issued by manage_buyer_finops_spend_passport."New value: +"Single-use unlock token issued by manage_buyer_finops_spend_passport."
    • changedInput schema / properties / preExecutionCallCheck / description
      Previous value: -"Optional pre-execution firewall check ({ toolName, argumentsPayload }) to block dangerous actions BEFORE execution."New value: +"Optional tool call payload to evaluate in the pre-execution firewall."
    • changedInput schema / properties / proposedTransactionAmountUsdc / description
      Previous value: -"Optional transaction amount in USDC to pre-check bilateral compatibility."New value: +"Optional USDC amount to check against buyer FinOps spend caps."
    • changedInput schema / properties / roleFilter / description
      Previous value: -"Filter directory by SELLER (1-3 Star Seals) or BUYER (FinOps Spend Passports)."New value: +"Filter directory output by SELLER or BUYER."
    • changedInput schema / properties / simulatedUpdateBehavior / description
      Previous value: -"Optional update payload ({ version, skillMarkdown, bundledScripts, declaredTools }) to test for Behavioral Drift (v1 vs v2)."New value: +"Optional update payload to evaluate version drift before deployment."
    • changedInput schema / properties / targetId / description
      Previous value: -"Store ID, Smart Contract ID, or Buyer Agent ID to inspect (or 'ALL' for the complete VERITAS-8183 directory)."New value: +"Store ID, agent ID, or 'ALL' for the full directory."
    • addedInput schema / properties / targetId / examples
      Added value: +[
      +  "trustgate-official-institutional"
      +]
    • changedInput schema / properties / versionToInspectOrUpdate / description
      Previous value: -"Optional agent/server version (e.g. '1.0.0' or '2.1.0') to compare against historical baseline for Behavioral Drift detection."New value: +"Agent version string to inspect for behavioral drift (v1 vs v2)."
  3. Changed3 schema fields changed
    • addedInput schema / properties / preExecutionCallCheck
      Added value: +{
      +  "description": "Optional pre-execution firewall check ({ toolName, argumentsPayload }) to block dangerous actions BEFORE execution.",
      +  "type": "object"
      +}
    • addedInput schema / properties / simulatedUpdateBehavior
      Added value: +{
      +  "description": "Optional update payload ({ version, skillMarkdown, bundledScripts, declaredTools }) to test for Behavioral Drift (v1 vs v2).",
      +  "type": "object"
      +}
    • addedInput schema / properties / versionToInspectOrUpdate
      Added value: +{
      +  "description": "Optional agent/server version (e.g. '1.0.0' or '2.1.0') to compare against historical baseline for Behavioral Drift detection.",
      +  "type": "string"
      +}
  4. Changed2 schema fields changed
    • changedInput schema / properties / callerSectorOrTrend / description
      Previous value: -"Optional: specify your industry sector or your user's shopping/search trend to personalize VERITAS-8183 telemetry."New value: +"Optional: specify ONE (1) single industry sector or keyword query to unlock WHO searched, HOW MANY TIMES, and with WHICH EXACT KEYWORDS (requires 1-time registration trial or 0.25 USDC per sector)."
    • addedInput schema / properties / forensicUnlockToken
      Added value: +{
      +  "description": "Optional 1-Time Single-Use Unlock Token issued by manage_buyer_finops_spend_passport.",
      +  "type": "string"
      +}
  5. Changed1 schema field changed
    • addedInput schema / properties / callerSectorOrTrend
      Added value: +{
      +  "description": "Optional: specify your industry sector or your user's shopping/search trend to personalize VERITAS-8183 telemetry.",
      +  "type": "string"
      +}
  6. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior, so the bar is lower. The description still adds real value by stating the call is free and that an empty call returns a read-only sample preview, which is material operational context not present in structured fields. It also hints that some depth requires an unlock token issued elsewhere.

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?

The bracketed registry tag and the 'Before trusting a seller' framing are front-loaded, and the value proposition follows immediately. It is compact with no filler, though the telegraphic style and the trailing preview sentence slightly dilute the focus.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nine-parameter tool with nested objects, the description only accounts for the core read path; the firewall, version-drift, and FinOps simulation parameters are left entirely to the schema. With no output schema, it does say what the seal and trust history represent, but not their format. Annotations cover safety, so this is adequate but incomplete for the tool's complexity.

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 all nine parameters are already documented in the schema. The description adds only a concrete usage example (targetId='ALL') and the empty-call preview pattern, which is helpful but marginal. Baseline 3 is appropriate when the schema carries the semantic load.

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?

The description names the concrete outputs an agent gets back: a 1-3 star seal, reserve ratio, trust history, and whether risky actions would be blocked. That is well beyond restating the opaque tool name, and it frames the resource as a seller's trust record. It does not name a sibling tool to distinguish itself from, which keeps it out of the top band.

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 phrase 'Before trusting a seller' gives a clear trigger context for selecting this tool. However, it never excludes conditions or points to alternatives such as get_trust_dossier_sample or check_mcp_server_trust for related checks, so the agent is left to infer when this one applies instead of its siblings.

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.