Skip to main content
Glama

submit_veritas_tier_upgrade_exam

[EN] VERITAS-8183 Seller & Smart Contract Tier Upgrade Exam (1-Star to 3-Star Institutional Gold Seal). Evaluates 5 hard pillars: Auditable Public Crypto Reserve Ratio (>=20% of operational volume for 3 Stars), Deterministic Code/Content Purity (>=98%), Verified Client Rating (>=4.8/5), Latency SLA (<=100ms), and Zero Slashing History. | [ES] Examen oficial de ascenso de nivel VERITAS-8183 (1 a 3 Estrellas) para vendedores y contratos inteligentes con verificación de Reserva Cripto Pública (>=20% del volumen) y calidad determinista. | [中文] VERITAS-8183 卖家与智能合约星级晋升考试(评估公开链上储备金比例 >=20%、内容质量、客户评分与响应时间以授予 1 至 3 星印章)。

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": {
      "storeId": "<storeId>"
    },
    "name": "submit_veritas_tier_upgrade_exam"
  }
}

Input Schema

NameRequiredDescriptionDefault
storeIdYes
verticalNo
storeNameNo
walletAddressNo
observedLatencyMsNo
sampleDeliverableNo
publicReserveWalletNoPublic auditable wallet holding the crypto reserve backing operations.
declaredMonthlyVolumeUsdcNoActive operational volume in USDC (3-Star Level 3 requires >=20% reserve-to-volume ratio).
declaredPublicReserveUsdcNoAuditable liquid/locked crypto reserve in USDC equivalent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the substantive grading criteria and the exact thresholds that determine 1-3 stars. It omits the operational traits that matter most for a mutation-like submission: whether a failed attempt is recorded, whether resubmission is allowed or rate-limited, whether any fee/escrow is touched, and whether the call is deterministic or performs live probing. Those gaps are meaningful for a tool with real consequences.

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

Conciseness3/5

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

The English lead is front-loaded with the pillar list, which is the useful part, but the same content is then restated in Spanish and Chinese at differing levels of detail, inflating length without adding new information for a single-language agent. The one-star-to-three-star framing and the passing thresholds are the only sentences that truly earn their place.

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 9-parameter submission tool with no annotations and no output schema, the description should say what a submission produces (awarded tier, per-pillar pass/fail, rejection reasons) and what the agent should do next. It supplies the grading rubric well but leaves the return semantics and failure handling entirely unstated.

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 coverage is only 33% (9 params, 1 required), so the description must compensate, and it partially does by tying the reserve-to-volume ratio and the 100ms latency bound to declaredPublicReserveUsdc, declaredMonthlyVolumeUsdc and observedLatencyMs. StoreId, vertical (an 8-value enum), storeName, walletAddress and the nested sampleDeliverable object remain unexplained in both schema and text.

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 action (tier upgrade exam submission) and resource (VERITAS-8183 seller/smart-contract certification) and enumerates the five evaluation pillars, which separates it from the read-only sibling inspect_veritas_8183_seal. It never says plainly that calling it submits a candidate for grading and returns a tier decision, so the verb is implied more by the name than the prose.

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 eligibility thresholds (>=20% reserve ratio, >=98% purity, >=4.8 rating, <=100ms) but no when-to-use guidance, no prerequisites (e.g., must the store already be registered or sealed first), and no mention of what happens on a failed attempt. No alternative tool is named as a substitute for a pre-check.

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.