Skip to main content
Glama

DJZS Trust MCP

by ai.djzs
OverviewDiscussionsAdmin

Verify Perpetual / Spot Trade Thesis (DJZS pre-execution audit)

verify_perp_trade

Deterministic pre-execution audit of a perpetual or spot TRADE thesis (direction, size, leverage, entry, stop, target, venue, and the REASON), run before capital is committed. USE THIS TOOL before opening, sizing, or increasing any perpetual or spot position. Returns PASS / WAIT / FAIL with a reproducible verdict hash. A position stated with no thesis FAILS (DJZS-S01); an unbounded position FAILS (DJZS-X01); an unresolvable stop or thesis WAITs. Prediction-market bets are refused here (use verify_pm_trade) and are not charged. Price 2.00 USDC per audit on Base.

Input Schema

NameRequiredDescriptionDefault
intentYesFree-text perpetual or spot trade thesis to audit: direction, size, leverage, entry, stop, target, venue, and the REASON
bracketNoOptional exact bracket (side, entry, stop, target, taker_fee_bps, optional hit_rate_pct / funding_rate_8h / sigma_annual). Returns the break-even hit rate in the non-scoring mechanics block; never enters the verdict or its hash
agent_addressNoOptional agent wallet (0x). If set, this audit updates that agent's on-chain DJZS trust score
target_systemNoOptional agent/project identifier. Written to the certificate ONLY with a matching target_system_subject + target_system_signature; unsigned values are DISCARDED, not stored
target_system_subjectNoAddress that signed the target_system claim. Must be the address that recovers from target_system_signature
target_system_signatureNoEIP-191 personal_sign over "DJZS-TSC-1 target-system claim\nsubject: <lowercased subject>\ntarget_system: <value>"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / bracket
      Added value: +{
+  "description": "Optional exact bracket (side, entry, stop, target, taker_fee_bps, optional hit_rate_pct / funding_rate_8h / sigma_annual). Returns the break-even hit rate in the non-scoring mechanics block; never enters the verdict or its hash",
+  "properties": {
+    "entry": {
+      "exclusiveMinimum": 0,
+      "type": "number"
+    },
+    "funding_rate_8h": {
+      "description": "Funding rate per 8 hours as a fraction (0.0001 = 0.01%); longs pay a positive rate. Counted only with sigma_annual",
+      "maximum": 0.05,
+      "minimum": -0.05,
+      "type": "number"
+    },
+    "hit_rate_pct": {
+      "description": "The thesis's stated probability, in percent, that the target prints before the stop",
+      "maximum": 99,
+      "minimum": 1,
+      "type": "number"
+    },
+    "side": {
+      "enum": [
+        "long",
+        "short"
+      ],
+      "type": "string"
+    },
+    "sigma_annual": {
+      "description": "Annualized volatility as a fraction (0.45 = 45%); sets the expected hold, and so the funding paid",
+      "exclusiveMinimum": 0,
+      "maximum": 10,
+      "type": "number"
+    },
+    "stop": {
+      "exclusiveMinimum": 0,
+      "type": "number"
+    },
+    "taker_fee_bps": {
+      "description": "The venue's taker fee in basis points, charged on entry and on exit",
+      "maximum": 100,
+      "minimum": 0,
+      "type": "number"
+    },
+    "target": {
+      "exclusiveMinimum": 0,
+      "type": "number"
+    }
+  },
+  "required": [
+    "side",
+    "entry",
+    "stop",
+    "target",
+    "taker_fee_bps"
+  ],
+  "type": "object"
+}
  2. Changed3 schema fields changed
    • changedInput schema / properties / target_system / description
      Previous value: -"Optional agent/project identifier; becomes the Target-System tag on the anchored PoL certificate"New value: +"Optional agent/project identifier. Written to the certificate ONLY with a matching target_system_subject + target_system_signature; unsigned values are DISCARDED, not stored"
    • addedInput schema / properties / target_system_signature
      Added value: +{
+  "description": "EIP-191 personal_sign over \"DJZS-TSC-1 target-system claim\\nsubject: <lowercased subject>\\ntarget_system: <value>\"",
+  "pattern": "^0x[0-9a-fA-F]{130}$",
+  "type": "string"
+}
    • addedInput schema / properties / target_system_subject
      Added value: +{
+  "description": "Address that signed the target_system claim. Must be the address that recovers from target_system_signature",
+  "pattern": "^0x[0-9a-fA-F]{40}$",
+  "type": "string"
+}
  3. Added

TDQS

A4.5/5.0
Behavior4/5

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

With only a title annotation, the description carries the burden and does well: it discloses the three possible verdicts (PASS/WAIT/FAIL), a reproducible verdict hash, the specific fail/wait rules (DJZS-S01, DJZS-X01, unresolvable stop), and the 2.00 USDC Base charge. It does not cover latency, idempotency, or what happens if payment fails, which keeps it short of a 5.

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

Conciseness5/5

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

The trigger ('USE THIS TOOL before...') is front-loaded right after the one-line purpose, followed by outcomes, failure rules, the sibling exclusion, and price. Every sentence carries distinct information with no repetition of the title or schema.

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

Completeness5/5

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

There is no output schema, yet the description names the return shape (PASS/WAIT/FAIL plus verdict hash) and the failure semantics, and it covers the cost and the excluded asset class. For a nested-schema audit tool this is sufficient for an agent to call it correctly.

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 schema already documents intent, bracket sub-fields, agent_address, and the target-system signing trio in detail. The description adds no per-parameter meaning beyond restating the thesis fields, so the baseline 3 is the right call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Deterministic pre-execution audit of a perpetual or spot TRADE thesis') and enumerates the audited dimensions (direction, size, leverage, entry, stop, target, venue, reason). It explicitly carves out prediction-market bets and routes them to the sibling verify_pm_trade, so an agent can separate it from that tool without opening either schema.

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

Usage Guidelines5/5

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

'USE THIS TOOL before opening, sizing, or increasing any perpetual or spot position' gives an explicit trigger condition, and the sentence about prediction-market bets being refused here with a pointer to verify_pm_trade gives the exclusion plus the alternative. Nothing about when to select this tool is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All DJZS Trust MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources