Skip to main content
Glama

veritas-8183-3star-rating-seal

submit_veritas_tier_upgrade_exam

[Public registry] Seller: take the exam (reserves, code purity, ratings, latency) to earn 1 to 3 trust stars that buyers can see. Example: storeId='prime-node'. 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": "submit_veritas_tier_upgrade_exam"
  }
}

Input Schema

NameRequiredDescriptionDefault
storeIdNoCandidate store identifier.
verticalNoTechnical vertical for the live exam.
storeNameNoDisplay name of the candidate node.
walletAddressNoPrimary operational wallet address.
observedLatencyMsNoMeasured P95 response latency in milliseconds.
sampleDeliverableNoDeliverable sample to audit during the exam.
publicReserveWalletNoPublic wallet holding auditable crypto reserves.
declaredMonthlyVolumeUsdcNoMonthly operational volume in USDC (>=20% reserve ratio required for 3 Stars).
declaredPublicReserveUsdcNoLiquid crypto reserve balance in USDC equivalent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
      -  "storeId"
      -]New value: +[]
  2. Changed9 schema fields changed
    • changedInput schema / properties / declaredMonthlyVolumeUsdc / description
      Previous value: -"Active operational volume in USDC (3-Star Level 3 requires >=20% reserve-to-volume ratio)."New value: +"Monthly operational volume in USDC (>=20% reserve ratio required for 3 Stars)."
    • changedInput schema / properties / declaredPublicReserveUsdc / description
      Previous value: -"Auditable liquid/locked crypto reserve in USDC equivalent."New value: +"Liquid crypto reserve balance in USDC equivalent."
    • addedInput schema / properties / observedLatencyMs / description
      Added value: +"Measured P95 response latency in milliseconds."
    • changedInput schema / properties / publicReserveWallet / description
      Previous value: -"Public auditable wallet holding the crypto reserve backing operations."New value: +"Public wallet holding auditable crypto reserves."
    • addedInput schema / properties / sampleDeliverable / description
      Added value: +"Deliverable sample to audit during the exam."
    • addedInput schema / properties / storeId / description
      Added value: +"Candidate store identifier."
    • addedInput schema / properties / storeName / description
      Added value: +"Display name of the candidate node."
    • addedInput schema / properties / vertical / description
      Added value: +"Technical vertical for the live exam."
    • addedInput schema / properties / walletAddress / description
      Added value: +"Primary operational wallet address."
  3. First observed

TDQS

B3.1/5.0
Behavior2/5

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

Annotations declare a non-read-only, non-idempotent, non-open-world operation, so the description must carry the weight of explaining side effects. It discloses that results are public ("[Public registry]", stars "that buyers can see"), which is valuable, but says nothing about cost, whether a submitted exam is final/retakeable, what happens on failure, or why a non-idempotent write accepts an empty call for a "read-only" preview.

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?

Two sentences with the audience tag and purpose front-loaded; the sample-preview mode is placed last where it belongs. The 'storeId=prime-node' example is filler that a 100%-covered schema already covers.

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

Completeness2/5

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

This is a 9-parameter, nested, non-idempotent submission with no output schema, and the description does not say what a submission returns (stars only? score breakdown?), whether partial submissions are accepted given required=[], or what the audit does with the sample deliverable. Too much of the calling contract is left to inference for a tool of this 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 the baseline is 3. The description adds only modest value: it maps the exam to reserves, code purity, ratings and latency, hinting at which parameters (reserve wallet, sample deliverable, declared volume) matter, plus a trivial storeId example; it does not explain the empty-object preview mode beyond a one-line mention.

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 gives a concrete verb and resource — take the exam to earn 1 to 3 trust stars visible to buyers — and names the graded dimensions (reserves, code purity, ratings, latency), so the operation is distinguishable from pure escrow/inspection siblings. It stops short of explicitly separating itself from a likely neighbour such as register_and_certify_store.

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?

Audience is stated ("Seller:") and one conditional usage mode is given ("Call with {} for a free read-only sample preview"), which is genuinely actionable. However, there is no guidance on when this is the wrong tool, sequencing relative to registration or certification, or prerequisites before submitting.

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.