Skip to main content
Glama

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'.

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
storeIdYesCandidate 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. 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."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already disclose readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the bar is lower; the description adds that this is a live exam scored on reserves/purity/ratings/latency with a 1–3 star outcome. It does not say whether the exam is persisted, whether retakes overwrite a prior grade, expected duration, or any cost, all material for a non-idempotent submission.

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 compact sentences with the registry tag, audience marker, and outcome front-loaded; every clause carries information. The trailing storeId example is a small extra but genuinely illustrates the one required parameter.

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 nine-parameter submission with no output schema, the description covers what the exam measures and what the result means (star tier). Missing is what a failed or partial exam returns and whether a grade is stored, which keeps it short of fully complete.

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% across all nine parameters, so the baseline is 3. The description loosely maps exam criteria to inputs (reserves to the reserve wallets, latency to observedLatencyMs, purity to sampleDeliverable) and gives a storeId example, but adds no format or constraint detail beyond the schema.

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 concrete verb and resource: take an exam covering reserves, code purity, ratings and latency to earn 1–3 trust stars visible to buyers. The seller-facing framing and the star outcome make the intent unmistakable, but it never distinguishes this from sibling flows like register_and_certify_store, so an agent cannot rank alternatives from the text alone.

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?

"Seller:" scopes the audience and the parenthetical lists the audit dimensions, implying the exam is for upgrading an existing store's tier. There is no explicit when-to-use versus register_and_certify_store or discover_verified_stores, and no guidance on re-taking, prerequisites, or consequences of failure, leaving the agent to infer.

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.