Skip to main content
Glama

inspect_veritas_8183_seal

[EN] FREE (<5ms) VERITAS-8183 Bilateral Quick-Glance Seal & Client Telemetry Inspector. Checks any Seller or Smart Contract's 1-to-3 Star Seal (Proof-of-Reserve >=20% crypto ratio, Content Quality, Verified Client Rating, Response Latency) AND any Buyer Agent's FinOps Spend Passport & VIP Discounts (5%-15% OFF). | [ES] Consulta gratuita en milisegundos del Sello VERITAS-8183 (1 a 3 Estrellas, Reserva Cripto Pública, Estadísticas de Clientes y Pasaporte de Solvencia/Descuentos del Comprador). | [中文] 免费毫秒级查询 VERITAS-8183 双向认证印章(卖家 1-3 星评级、>=20% 链上加密储备金证明、客户评价与延迟统计,以及买家 FinOps 预算护照与 VIP 折扣)。

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, Smart Contract ID, or Buyer Agent ID to inspect (or 'ALL' for the complete VERITAS-8183 directory).
roleFilterNoFilter directory by SELLER (1-3 Star Seals) or BUYER (FinOps Spend Passports).
callerSectorOrTrendNoOptional: specify your industry sector or your user's shopping/search trend to personalize VERITAS-8183 telemetry.
buyerIdForSimulationNoOptional buyer agent ID for bilateral pre-check.
proposedTransactionAmountUsdcNoOptional transaction amount in USDC to pre-check bilateral compatibility.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
      +}
  2. First observed

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose that the operation is a free, sub-5ms read-style inspection covering both counterparty sides, which implies non-destructive behavior. However, it never states permission/auth requirements, rate limits, pagination, or what a 'Seal' result actually contains, and it never explicitly asserts that the call has no side effects on the inspected records.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is triplicated across English, Spanish, and Chinese, so roughly two-thirds of the text carries no new information for a single-language reader. It is front-loaded with marketing noise ('FREE (<5ms)', 'Quick-Glance') ahead of the substantive scope statement. The underlying message is one sentence's worth of content inflated into a paragraph.

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 5-parameter, all-optional inspection tool with full schema coverage and no annotations or output schema, the description covers the domain scope adequately: it tells the agent that both seller seals and buyer passports are retrievable and what criteria feed the seal. What is missing is the shape of a result and whether a bilateral pre-check returns a compatibility verdict, which matters because there is no output schema to fall back on.

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 every parameter (targetId, roleFilter, callerSectorOrTrend, buyerIdForSimulation, proposedTransactionAmountUsdc) is already documented in the schema, and the baseline is 3. The description adds only high-level framing of the bilateral SELLER/BUYER split, which loosely motivates roleFilter, but it does not explain 'ALL' directory mode or the simulation parameters beyond what the schema already says.

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 a concrete verb ('Checks'/'Inspector') and enumerates exactly what is inspected: a seller/smart-contract 1-to-3 Star Seal (proof-of-reserve >=20%, content quality, client rating, response latency) and a buyer agent's FinOps Spend Passport and VIP discounts. That is specific enough to distinguish it from the audit_*_escrow siblings. Clarity is reduced by proprietary jargon ('Seal', 'FinOps Spend Passport', 'telemetry') that is never defined, and by the fact that the same statement is repeated three times in different languages rather than expanded.

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

Usage Guidelines2/5

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

The description gives no when-to-use or when-not-to-use guidance, and never names an alternative such as manage_buyer_finops_spend_passport or discover_verified_stores, even though the buyer-passport overlap is obvious. The only usage-adjacent claims are marketing ('FREE', '<5ms'), which tell the agent about cost/latency but not about selection. Any sense of 'use this to pre-check a counterparty' must be inferred from the schema's buyerIdForSimulation description, not from this text.

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.