Agenda Intelligence MD
Server Details
Evidence-readiness MCP server: validate, audit, and score briefs, memos, and evidence packs.
- Status
- Healthy
- Uptime
- 100.0% over 37 days
- Last Tested
- Transport
- Streamable HTTP ยท MCP 2025-11-25
- URL
- Repository
- vassiliylakhonin/agenda-intelligence-md
- GitHub Stars
- 8
- Server Listing
- Agenda Intelligence
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion with other tools. The tool's purpose is clearly stated as escrow arbitration and delivery verification, so an agent can easily identify its function.
The single tool name follows a descriptive snake_case pattern (m2m_escrow_arbitration_ruling), which is internally consistent. With no other tools to compare, consistency is trivially achieved.
The server offers only 1 tool, which feels thin for a domain that likely involves multiple operations (e.g., escrow creation, funding, settlement). However, the tool itself is complex and self-contained, so it's not egregiously inappropriate.
The tool only performs arbitration ruling and explicitly does not handle settlement or clearance. For a complete escrow lifecycle, tools for creating escrows, submitting deliveries, raising disputes, and executing settlements would be expected. Significant gaps exist.
Available Tools
1 toolm2m_escrow_arbitration_rulingARead-onlyIdempotentInspect
Deterministic dispute arbitration and delivery verification for Agent-to-Agent escrow transactions. Checks supplied hashes, supported offline JSON schemas and deadlines, proposing allocations for human review. No settlement or clearance is issued. Required tool arguments: request. Grades supplied evidence; it does not independently verify source truth. Obtain the source records requested by inputSchema before asking for a decision-ready result. Do not fabricate missing evidence. Illustrative example arguments (synthetic; replace with your own data): {"request":{"escrow_id":"escrow-m2m-sample-001","dispute_claim":{"claimant":"buyer","reason":"Contract deliverable dispute"},"deal_terms":{"buyer_id":"did:agent:0x1111111111111111111111111111111111111111","seller_id":"did:agent:0x2222222222222222222222222222222222222222","amount_usd":500,"currency":"USDC","deadline_utc":"2026-09-17T18:00:00Z","arbitration_policy":"pro_rata","arbitration_fee_pct":1},"specification":{"deliverable_type":"json_data","min_valid_records_pct":95},"delivery_submission":{"submitted_at":"2026-09-17T12:00:00Z","telemetry":{"total_items":1000,"valid_items":1000,"response_time_ms":320}}}}. Evaluation requires a signed Base USDC payment for the exact request, or Pro access. Discovery is free. Keep the original request and X-Payment-Signature for result recovery within 24 hours. Current prices: https://m2m-escrow-arbiter-a2a.vassiliy-lakhonin.workers.dev/.well-known/x402. Do not pay automatically. Evidence triage only: no factual-truth verification, no legal, compliance, sanctions, or financial advice. Human review is required before any commercial action.
| Name | Required | Description | Default |
|---|---|---|---|
| request | Yes | Structured request object. Full contract: https://github.com/vassiliylakhonin/agenda-intelligence-md/blob/main/schemas/v1/m2m-escrow-arbiter-request.schema.json |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: no settlement is issued, this is evidence triage only with no factual-truth verification, grades supplied evidence rather than independently verifying source truth, requires x402 payment, and results are recoverable for 24 hours with the original request and signature.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with the core purpose and negative scope before logistics. The synthetic example and payment/disclaimer details all earn their place, but the passage is long and the disclaimers repeat the 'no verification / human review' theme more than once, costing some tightness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a complex tool with a nested request object backed by an external schema and an existing output schema, the description covers prerequisites, payment, scope limits, and evidence-handling rules adequately; return values need not be explained since an output schema exists.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Only one parameter with 100% schema description coverage whose schema is an external contract link, so the baseline is 3. The description significantly compensates by supplying a full illustrative, nested example argument showing escrow_id, dispute_claim, deal_terms, specification, and delivery_submission structure, which goes well beyond the terse schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource: deterministic dispute arbitration and delivery verification for A2A escrow transactions. It also delineates scope precisely by declaring what it does NOT do (no settlement or clearance is issued), so an agent knows exactly where the tool's authority ends.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states prerequisites ('Obtain the source records requested by inputSchema before asking for a decision-ready result'), prohibitions ('Do not fabricate missing evidence'), payment conditions ('requires a signed Base USDC payment... or Pro access; Discovery is free'), and that human review is required before commercial action.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
m2m_escrow_arbitration_ruling1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "https://json-schema.org/draft/2020-12/schema", + "anyOf": [ + { + "$schema": "https://json-schema.org/draft/2020-12/schema", + "additionalProperties": false, + "description": "Response contract for delivery-evidence review. Unverified delivery requires human review and cannot authorize settlement.", + "properties": { + "arbitration_ruling": { + "properties": { + "check_status": { + "additionalProperties": { + "enum": [ + "passed", + "failed", + "not_evaluated", + "not_applicable" + ] + }, + "type": "object" + }, + "checks": { + "properties": { + "deadline_honored": { + "type": "boolean" + }, + "hash_verified": { + "type": "boolean" + }, + "schema_verified": { + "type": "boolean" + }, + "slo_verified": { + "type": "boolean" + } + }, + "required": [ + "deadline_honored", + "hash_verified", + "schema_verified", + "slo_verified" + ], + "type": "object" + }, + "escrow_id": { + "type": "string" + }, + "evaluation_scope": { + "type": "string" + }, + "evidence_gaps": { + "items": { + "type": "string" + }, + "type": "array" + }, + "execution_advisory": { + "type": "string" + }, + "payout_breakdown": { + "properties": { + "arbiter_fee_usd": { + "type": "number" + }, + "buyer_refund_usd": { + "type": "number" + }, + "seller_payout_usd": { + "type": "number" + }, + "total_escrow_usd": { + "type": "number" + } + }, + "required": [ + "total_escrow_usd", + "seller_payout_usd", + "buyer_refund_usd", + "arbiter_fee_usd" + ], + "type": "object" + }, + "ruling": { + "enum": [ + "RELEASE_TO_SELLER", + "REFUND_TO_BUYER", + "PARTIAL_SETTLEMENT", + "ESCALATE_HUMAN" + ], + "type": "string" + }, + "score": { + "type": "integer" + }, + "settlement_authorized": { + "const": false, + "type": "boolean" + }, + "status": { + "enum": [ + "decision_ready", + "not_decision_ready", + "escalate" + ], + "type": "string" + }, + "violations": { + "items": { + "type": "string" + }, + "type": "array" + }, + "vizier_clearance_receipt": { + "type": [ + "string", + "null" + ] + }, + "vizier_status": { + "type": "string" + } + }, + "required": [ + "status", + "ruling", + "score", + "escrow_id", + "payout_breakdown", + "checks", + "violations", + "evidence_gaps" + ], + "type": "object" + }, + "contract_version": { + "type": "string" + }, + "profile": { + "const": "m2m_escrow_arbiter", + "type": "string" + } + }, + "required": [ + "contract_version", + "profile", + "arbitration_ruling" + ], + "title": "M2MEscrowArbiterResponse", + "type": "object", + "x-schema-version": "1" + }, + { + "properties": { + "artifacts": { + "items": { + "type": "object" + }, + "type": "array" + }, + "id": { + "type": "string" + }, + "metadata": { + "properties": { + "human_review_required": { + "const": true + }, + "response": { + "$schema": "https://json-schema.org/draft/2020-12/schema", + "additionalProperties": false, + "description": "Response contract for delivery-evidence review. Unverified delivery requires human review and cannot authorize settlement.", + "properties": { + "arbitration_ruling": { + "properties": { + "check_status": { + "additionalProperties": { + "enum": [ + "passed", + "failed", + "not_evaluated", + "not_applicable" + ] + }, + "type": "object" + }, + "checks": { + "properties": { + "deadline_honored": { + "type": "boolean" + }, + "hash_verified": { + "type": "boolean" + }, + "schema_verified": { + "type": "boolean" + }, + "slo_verified": { + "type": "boolean" + } + }, + "required": [ + "deadline_honored", + "hash_verified", + "schema_verified", + "slo_verified" + ], + "type": "object" + }, + "escrow_id": { + "type": "string" + }, + "evaluation_scope": { + "type": "string" + }, + "evidence_gaps": { + "items": { + "type": "string" + }, + "type": "array" + }, + "execution_advisory": { + "type": "string" + }, + "payout_breakdown": { + "properties": { + "arbiter_fee_usd": { + "type": "number" + }, + "buyer_refund_usd": { + "type": "number" + }, + "seller_payout_usd": { + "type": "number" + }, + "total_escrow_usd": { + "type": "number" + } + }, + "required": [ + "total_escrow_usd", + "seller_payout_usd", + "buyer_refund_usd", + "arbiter_fee_usd" + ], + "type": "object" + }, + "ruling": { + "enum": [ + "RELEASE_TO_SELLER", + "REFUND_TO_BUYER", + "PARTIAL_SETTLEMENT", + "ESCALATE_HUMAN" + ], + "type": "string" + }, + "score": { + "type": "integer" + }, + "settlement_authorized": { + "const": false, + "type": "boolean" + }, + "status": { + "enum": [ + "decision_ready", + "not_decision_ready", + "escalate" + ], + "type": "string" + }, + "violations": { + "items": { + "type": "string" + }, + "type": "array" + }, + "vizier_clearance_receipt": { + "type": [ + "string", + "null" + ] + }, + "vizier_status": { + "type": "string" + } + }, + "required": [ + "status", + "ruling", + "score", + "escrow_id", + "payout_breakdown", + "checks", + "violations", + "evidence_gaps" + ], + "type": "object" + }, + "contract_version": { + "type": "string" + }, + "profile": { + "const": "m2m_escrow_arbiter", + "type": "string" + } + }, + "required": [ + "contract_version", + "profile", + "arbitration_ruling" + ], + "title": "M2MEscrowArbiterResponse", + "type": "object", + "x-schema-version": "1" + } + }, + "required": [ + "response", + "human_review_required" + ], + "type": "object" + }, + "status": { + "properties": { + "state": { + "type": "string" + } + }, + "required": [ + "state" + ], + "type": "object" + } + }, + "required": [ + "id", + "status", + "artifacts", + "metadata" + ], + "type": "object" + } + ], + "title": "M2MEscrowArbiterResponseMcpCompatibility", + "type": "object" +}
2 tool updates
- Removed
dual_use_technology_export - Added
m2m_escrow_arbitration_ruling
1 tool update
- First observed
dual_use_technology_export
Related MCP Connectors
MCP server providing access to the Scorecard API to evaluate and optimize LLM systems.
The evidence layer for MCP: live operational grades plus Trust Receipts for every registry server.
A paid remote MCP for CLI tool MCP, built to return verdicts, receipts, usage logs, and audit-ready
MCP-native AI evaluation: rubric audits, eval suites, and proof reports for AI/LLM output.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEvidence-first delivery audit MCP server that evaluates task requirements against delivery evidence and returns a reproducible pass/needs_review/fail decision with a deterministic receipt.MIT
- AlicenseAqualityCmaintenanceMCP server for Tru8 Evidence Research that enables AI agents to submit claims or URLs and receive source-traced evidence organized by tier and type with element decomposition and relationship mapping.339 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceMCP server for AI compliance auditing. Scores agent outputs for hallucination liability under the EU AI Act, issues verifiable compliance stamps, and tracks audit history by agent.MIT
- AlicenseBqualityAmaintenanceLocal-first MCP server that transforms civil case PDFs into queryable cases with structural provenance, evidence IDs, and page-level verification for drafting and factual review.22Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.