MVR API - Minimum Viable Relationships

Check evidence completeness

mvr_evidence_completeness

Read-only

Use after entity resolution and before any readiness claim to check verification status, source-family diversity, stakeholder coverage, and missing proof. Do not treat completeness as authorization. Use when: Use after entity resolution and before any verdict when evidence may be incomplete or one-sided. Do not use when: Do not treat completeness as readiness or authorization. Submit only consented, data-minimized, redacted or aggregated evidence; never raw private interviews, secrets, credentials, or personal identifiers.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`payload`	Yes	Evidence pack and decision context to test for missing proof.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	No
`next_steps`	No
`workflow_id`	No
`evidence_gaps`	No
`mcp_next_call`	No
`mcp_next_tool`	No
`response_meta`	No
`evidence_count`	No
`workflow_status`	No
`safe_next_action`	No
`verification_basis`	No
`workflow_expires_at`	No
`mvr_response_receipt`	No
`required_user_inputs`	No
`stakeholder_coverage`	No
`verified_evidence_count`	No
`continuation_disposition`	No
`verified_source_families`	No
`unverified_evidence_count`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedSep 5, 2026

addedOutput schema / properties / next_steps

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "automatic_action_authorized": {
+      "const": false,
+      "type": "boolean"
+    },
+    "boundary": {
+      "type": "string"
+    },
+    "offer_registry": {
+      "format": "uri",
+      "type": "string"
+    },
+    "options": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "label": {
+            "type": "string"
+          },
+          "url": {
+            "format": "uri",
+            "type": "string"
+          },
+          "when_to_use": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "label",
+          "url",
+          "when_to_use"
+        ],
+        "type": "object"
+      },
+      "maxItems": 3,
+      "type": "array"
+    },
+    "purpose": {
+      "const": "optional_routing_not_recommendation",
+      "type": "string"
+    },
+    "schema_version": {
+      "const": "mvr-optional-routing@1.0",
+      "type": "string"
+    }
+  },
+  "required": [
+    "schema_version",
+    "purpose",
+    "automatic_action_authorized",
+    "boundary",
+    "offer_registry",
+    "options"
+  ],
+  "type": "object"
+}

Changed7 schema fields changedAug 11, 2026

addedOutput schema / properties / continuation_disposition

Added value: +{
+  "enum": [
+    "call_now",
+    "await_input",
+    "terminal"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / mcp_next_call

Added value: +{
+  "anyOf": [
+    {
+      "type": "null"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "arguments": {
+          "additionalProperties": false,
+          "properties": {
+            "payload": {
+              "additionalProperties": true,
+              "type": "object"
+            }
+          },
+          "required": [
+            "payload"
+          ],
+          "type": "object"
+        },
+        "name": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "name",
+        "arguments"
+      ],
+      "type": "object"
+    }
+  ]
+}

addedOutput schema / properties / mcp_next_tool

Added value: +{
+  "anyOf": [
+    {
+      "type": "null"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "arguments": {
+          "additionalProperties": false,
+          "properties": {
+            "payload": {
+              "additionalProperties": true,
+              "type": "object"
+            }
+          },
+          "required": [
+            "payload"
+          ],
+          "type": "object"
+        },
+        "tool_name": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "tool_name",
+        "arguments"
+      ],
+      "type": "object"
+    }
+  ]
+}

addedOutput schema / properties / required_user_inputs

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / workflow_expires_at

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / workflow_id

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / workflow_status
```
Added value: +{
+  "type": "string"
+}
```

Changed2 schema fields changedJul 29, 2026

addedOutput schema / properties / mvr_response_receipt / properties / mcp_protocol_versions
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```

changedOutput schema / properties / mvr_response_receipt / required

Previous value: -[
-  "receipt_schema_version",
-  "mcp_tool",
-  "core_api_version",
-  "mcp_contract_version",
-  "tool_profile_version",
-  "sdk_version",
-  "policy_version",
-  "calibration_version",
-  "deployment_revision",
-  "host_recipe_version",
-  "authority_boundary"
-]New value: +[
+  "receipt_schema_version",
+  "mcp_tool",
+  "core_api_version",
+  "mcp_protocol_versions",
+  "mcp_contract_version",
+  "tool_profile_version",
+  "sdk_version",
+  "policy_version",
+  "calibration_version",
+  "deployment_revision",
+  "host_recipe_version",
+  "authority_boundary"
+]

Changed1 schema field changedJul 27, 2026

addedOutput schema / properties / mvr_response_receipt

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "authority_boundary": {
+      "type": "string"
+    },
+    "calibration_version": {
+      "type": "string"
+    },
+    "core_api_version": {
+      "type": "string"
+    },
+    "deployment_revision": {
+      "type": "string"
+    },
+    "host_recipe_version": {
+      "type": "string"
+    },
+    "mcp_contract_version": {
+      "type": "string"
+    },
+    "mcp_tool": {
+      "type": "string"
+    },
+    "policy_version": {
+      "type": "string"
+    },
+    "receipt_schema_version": {
+      "type": "string"
+    },
+    "sdk_version": {
+      "type": "string"
+    },
+    "tool_profile_version": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "receipt_schema_version",
+    "mcp_tool",
+    "core_api_version",
+    "mcp_contract_version",
+    "tool_profile_version",
+    "sdk_version",
+    "policy_version",
+    "calibration_version",
+    "deployment_revision",
+    "host_recipe_version",
+    "authority_boundary"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJul 15, 2026
- addedOutput schema / properties / verification_basis
```
Added value: +{
+  "type": "string"
+}
```

Changed7 schema fields changedJul 12, 2026

addedInput schema / properties / payload / properties / evidence_pack / items / properties / evidence_origin

Added value: +{
+  "description": "Alias for source_class when the host uses evidence-origin terminology.",
+  "type": "string"
+}

addedInput schema / properties / payload / properties / evidence_pack / items / properties / load_bearing

Added value: +{
+  "description": "True when this item materially supports the target recommendation.",
+  "type": "boolean"
+}

addedInput schema / properties / payload / properties / evidence_pack / items / properties / source_class

Added value: +{
+  "description": "Origin family, for example entity_reported, structured_field_research, regulator_published, or counterparty_reference.",
+  "type": "string"
+}

addedInput schema / properties / payload / properties / evidence_pack / items / properties / verification_status / enum

Added value: +[
+  "unverified",
+  "verified",
+  "independently_verified",
+  "corroborated",
+  "attested",
+  "confirmed",
+  "validated"
+]

addedOutput schema / properties / unverified_evidence_count
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / verified_evidence_count
```
Added value: +{
+  "type": "number"
+}
```

addedOutput schema / properties / verified_source_families

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed2 schema fields changedJul 12, 2026

changedInput schema / properties / payload / description

Previous value: -"Evidence-completeness request body."New value: +"Evidence pack and decision context to test for missing proof."

addedInput schema / properties / payload / properties

Added value: +{
+  "decision_stage": {
+    "description": "Idea, pre-entry, pilot, launch, expansion, or scale stage.",
+    "type": "string"
+  },
+  "evidence_items": {
+    "description": "Alias for evidence_pack when the host already uses this field name.",
+    "items": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "evidence_pack": {
+    "description": "Evidence items available for the decision.",
+    "items": {
+      "additionalProperties": true,
+      "properties": {
+        "claim": {
+          "type": "string"
+        },
+        "evidence_type": {
+          "type": "string"
+        },
+        "id": {
+          "type": "string"
+        },
+        "source_date": {
+          "type": "string"
+        },
+        "source_grade": {
+          "type": "string"
+        },
+        "source_url": {
+          "type": "string"
+        },
+        "stakeholder_class": {
+          "type": "string"
+        },
+        "verification_status": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "market_scope": {
+    "additionalProperties": true,
+    "description": "Geography in which the evidence must be valid.",
+    "properties": {
+      "city": {
+        "type": "string"
+      },
+      "corridor": {
+        "type": "string"
+      },
+      "country": {
+        "type": "string"
+      },
+      "region": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "subject": {
+    "additionalProperties": true,
+    "description": "Resolved or supplied entity under assessment.",
+    "properties": {
+      "entity_archetype": {
+        "type": "string"
+      },
+      "entity_name": {
+        "type": "string"
+      },
+      "sector": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "target_claim": {
+    "description": "Claim or readiness question the evidence is meant to support.",
+    "type": "string"
+  }
+}

Changed1 schema field changedJul 11, 2026
- removedInput schema / properties / api_key
```
Removed value: -{
-  "type": "string"
-}
```

Changed1 schema field changedMay 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "evidence_count": {
+      "type": "number"
+    },
+    "evidence_gaps": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "response_meta": {
+      "type": "object"
+    },
+    "safe_next_action": {
+      "type": "string"
+    },
+    "stakeholder_coverage": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "status": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedMay 24, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description consistently describes a read-only check. It adds meaningful behavioral context by warning that completeness is not authorization and by imposing input constraints: submit only consented, data-minimized, redacted or aggregated evidence, never raw private data or credentials. No contradiction with annotations.

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

Conciseness3/5

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

The content is useful and front-loaded, but it is redundant: 'Use after entity resolution and before any readiness claim' is repeated in the 'Use when' section, and the authorization disclaimer appears twice with slightly different wording. Tightening these would make it cleaner without losing meaning.

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?

Given an output schema is present and annotations cover safety, the description is complete: it states when to use the tool, what it checks, when not to use it, and input privacy requirements. The one-parameter payload and fully described schema mean no critical usage context is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value by naming the analytical dimensions the tool evaluates—verification status, source-family diversity, stakeholder coverage—which map to fields like verification_status and source_class, helping the agent know what evidence attributes matter when building the payload.

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?

The description states a specific verb and resource: 'check evidence completeness' with concrete dimensions—verification status, source-family diversity, stakeholder coverage, and missing proof. It also positions the tool in the workflow ('after entity resolution and before any verdict'), distinguishing it from mvr_entity_resolve and mvr_decision_check.

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

Usage Guidelines4/5

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

The description gives explicit 'Use when' and 'Do not use when' guidance, including the crucial caveat not to treat completeness as readiness or authorization. It does not name an alternative sibling tool directly, but the workflow placement ('after entity resolution and before any verdict') implies routing away from entity resolution and decision tools.

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

All MVR API - Minimum Viable Relationships tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation4/5

Each tool occupies a distinct workflow stage: preflight, entity resolution, evidence completeness, context compilation, and decision routing. However, evidence gaps are checked by both mvr_first_call and mvr_evidence_completeness, and mvr_decision_check also references missing proof, creating mild boundary overlap.

Naming Consistency4/5

All tools share a consistent mvr_ prefix and snake_case style, which aids recognition. The suffix pattern is slightly inconsistent—some are noun_verb (entity_resolve, context_compile, decision_check) while first_call and evidence_completeness use different grammatical forms—but the overall pattern remains predictable.

Tool Count5/5

Five tools is well-scoped for a public decision-governance preflight workflow. Each tool maps to a necessary phase and none feel redundant or extraneous.

Completeness5/5

The tool set covers the entire public preflight lifecycle: initial governance check, entity resolution, evidence completeness verification, context compilation, and final routing to licensed scoring or abstention. The licensed scoring step is intentionally external, so no critical operation appears missing for the stated purpose.

Check evidence completeness

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources