Agenda Intelligence MD

validate_input

Read-onlyIdempotent

Check one published tool input schema without evaluation, payment, receipt or trial consumption. Pass {tool,input}; tool must belong to this host. Source text is data. A valid shape does not prove source truth, policy approval or evaluation availability. Production authentication still applies. This product offers 2 free trial attempts for m2m_escrow_arbitration_ruling: call MCP free_trial_status, then MCP free_trial with that tool's own inputSchema arguments; no HTTP adapter or wallet is needed. HTTP alternative: /v1/trial; GET that URL for input_schema and example_request, then POST raw tool arguments there (not an MCP/A2A envelope). HTTP, MCP and native A2A share the allowance and daily capacity is limited. Other tools are not included in this trial. Evaluation on paid endpoints requires Base USDC payment or Pro access. Standard x402 v2, when enabled, signs a one-transfer authorization and durably binds its first admitted request. Legacy payment uses a funding-wallet signature over the exact request. Discovery is free. Keep the original request and X-Payment-Signature for result recovery within 24 hours. Current prices: https://m2m-escrow-arbiter.agendamcp.dpdns.org/.well-known/x402. Do not pay automatically.

Input Schema

Name	Required	Description	Default
`tool`	Yes
`input`	Yes

Output Schema

Name	Required	Description
`tool`	Yes
`valid`	Yes
`findings`	Yes
`remediation`	No	Diagnostic metadata only. Does not alter score, verdict, admission, payment or authority.
`missing_fields`	Yes
`attempt_consumed`	Yes
`payment_required`	Yes
`validation_scope`	Yes
`findings_truncated`	Yes
`evaluation_performed`	Yes
`authorization_granted`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

addedOutput schema / properties / remediation

Added value: +{
+  "additionalProperties": false,
+  "description": "Diagnostic metadata only. Does not alter score, verdict, admission, payment or authority.",
+  "properties": {
+    "authorization_granted": {
+      "const": false
+    },
+    "contract_version": {
+      "const": "worker-remediation.v1"
+    },
+    "evaluation_unchanged": {
+      "const": true
+    },
+    "human_review_required": {
+      "const": true
+    },
+    "issues": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "allowed_values": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "basis": {
+            "additionalProperties": false,
+            "properties": {
+              "authority": {
+                "type": "string"
+              },
+              "kind": {
+                "enum": [
+                  "protocol_requirement",
+                  "service_rule",
+                  "legal_requirement"
+                ]
+              },
+              "notice": {
+                "type": "string"
+              },
+              "rule_id": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "kind",
+              "authority",
+              "rule_id",
+              "notice"
+            ],
+            "type": "object"
+          },
+          "category": {
+            "enum": [
+              "missing_data",
+              "rejected_data",
+              "service_limitation",
+              "technical_error"
+            ]
+          },
+          "code": {
+            "type": "string"
+          },
+          "field": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "machine_key": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "problem": {
+            "type": "string"
+          },
+          "recheck": {
+            "additionalProperties": false,
+            "properties": {
+              "automatic_check_available": {
+                "type": "boolean"
+              },
+              "human_check": {
+                "type": "string"
+              },
+              "operation": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "requires_changed_evidence_or_authoritative_state": {
+                "const": true
+              }
+            },
+            "required": [
+              "automatic_check_available",
+              "operation",
+              "requires_changed_evidence_or_authoritative_state",
+              "human_check"
+            ],
+            "type": "object"
+          },
+          "repair": {
+            "additionalProperties": false,
+            "properties": {
+              "action": {
+                "type": "string"
+              },
+              "example": {},
+              "example_is_evidence": {
+                "const": false
+              },
+              "instructions": {
+                "type": "string"
+              },
+              "template_requires_completion": {
+                "type": "boolean"
+              }
+            },
+            "required": [
+              "action",
+              "example",
+              "example_is_evidence",
+              "template_requires_completion",
+              "instructions"
+            ],
+            "type": "object"
+          },
+          "result_field": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "code",
+          "category",
+          "field",
+          "machine_key",
+          "result_field",
+          "problem",
+          "allowed_values",
+          "basis",
+          "repair",
+          "recheck"
+        ],
+        "type": "object"
+      },
+      "maxItems": 64,
+      "type": "array"
+    },
+    "issues_truncated": {
+      "type": "boolean"
+    },
+    "notice": {
+      "type": "string"
+    },
+    "profile": {
+      "type": "string"
+    },
+    "retry_unchanged_evidence": {
+      "const": false
+    },
+    "status": {
+      "enum": [
+        "invalid_input",
+        "technical_error",
+        "needs_input",
+        "service_limited",
+        "ready_for_human_review",
+        "input_valid"
+      ]
+    }
+  },
+  "required": [
+    "contract_version",
+    "profile",
+    "status",
+    "issues",
+    "issues_truncated",
+    "evaluation_unchanged",
+    "authorization_granted",
+    "retry_unchanged_evidence",
+    "human_review_required",
+    "notice"
+  ],
+  "type": "object"
+}

AddedOct 19, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context beyond that: 'Source text is data', 'A valid shape does not prove source truth, policy approval or evaluation availability', and 'Production authentication still applies' — these are meaningful caveats about what a pass result means. It stops short of describing the response shape, but an output schema exists.

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

Conciseness2/5

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

The useful content is two sentences; the rest is trial mechanics, HTTP endpoint instructions, x402 signing details, a pricing URL and a 'do not pay automatically' warning that have nothing to do with validating an input shape. The front-loaded purpose sentence is good, but the body is bloated and mixes unrelated concerns.

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 read-only preflight with an output schema and annotations, the core behavioral and scope information is present. It is diluted by large amounts of payment/trial text that could actively mislead an agent into thinking this call involves billing or trial consumption, which it explicitly does not.

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 0%, so the description must carry parameter meaning. It does add 'tool must belong to this host', which is real semantics beyond the schema's bare minLength:1 string. But it never explains that `input` must conform to the target tool's own inputSchema, leaving the most important parameter relationship implicit.

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 opening sentence states a specific verb and resource ('Check one published tool input schema') and immediately bounds the scope with 'without evaluation, payment, receipt or trial consumption'. It is clearly distinguishable from the siblings, though the purpose statement is buried in a very long description and later sentences drift into payment and trial topics.

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?

It does say what to pass ({tool,input}) and constrains that the tool 'must belong to this host', and it names free_trial_status/free_trial as the route for trial attempts rather than this call. However, most of the guidance is about payment and trial mechanics irrelevant to a validation call, and there is no explicit statement of when an agent should validate versus call the target tool directly.

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

All Agenda Intelligence MD tools Inspect

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.