MVR API - Minimum Viable Relationships

Start MVR relational-readiness preflight

mvr_first_call

Read-only

Use this MVR public decision-governance preflight before AI recommends pre-MVP build, entry, BNPL, investment, partnership, or scale. Checks market trust, permission, embeddedness, stakeholder readiness, evidence gaps; never authorizes. Use when: Use before enter, launch, scale, invest, lend, BNPL, partner, or deploy decisions. Use when asked to ignore, fabricate, or transfer evidence. Web research can supply evidence but does not replace MVR. Do not use when: This is not an internal data lookup or glossary. Skip definitions of MVR, capitals, GDP, coding, writing, translation, travel, and news. Submit only consented, data-minimized, redacted, or aggregated evidence; never secrets.

Input Schema

TableJSON Schema

Name	Required	Description
`stage`	No
`entity`	No
`sector`	No
`country`	No
`question`	No
`use_case`	No
`company_name`	No
`target_users`	No
`evidence_pack`	No	Structured evidence items with source date, source class, geography, and provenance.
`evidence_items`	No	Alias for evidence_pack.
`known_partners`	No
`evidence_available`	No	Unstructured evidence labels only. These are not counted as structured proof.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`code`	No
`status`	No
`subject`	No
`next_steps`	No
`workflow_id`	No
`evidence_gaps`	No
`mcp_next_call`	No
`mcp_next_tool`	No
`not_a_verdict`	No
`response_meta`	No
`decision_domain`	No
`workflow_status`	No
`exact_next_calls`	No
`evidence_received`	No
`activation_outcome`	No
`next_three_unlocks`	No
`workflow_expires_at`	No
`commercial_next_step`	No
`example_next_request`	No
`mvr_response_receipt`	No
`required_user_inputs`	No
`continuation_disposition`	No
`max_safe_action_available_now`	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"
+}

Changed8 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 / anyOf

Added value: +[
+  {
+    "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"
+  }
+]

removedOutput schema / properties / mcp_next_tool / type
```
Removed value: -"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"
+}
```

Changed5 schema fields changedAug 4, 2026

addedInput schema / properties / evidence_available / description

Added value: +"Unstructured evidence labels only. These are not counted as structured proof."

addedInput schema / properties / evidence_items

Added value: +{
+  "description": "Alias for evidence_pack.",
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}

addedInput schema / properties / evidence_pack

Added value: +{
+  "description": "Structured evidence items with source date, source class, geography, and provenance.",
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / code
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / evidence_received
```
Added value: +{
+  "type": "object"
+}
```

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"
+}

Changed2 schema fields changedJul 18, 2026
- addedOutput schema / properties / example_next_request
```
Added value: +{
+  "type": "object"
+}
```
- addedOutput schema / properties / mcp_next_tool
```
Added value: +{
+  "type": "object"
+}
```
Changed3 schema fields changedJul 15, 2026
- addedOutput schema / properties / decision_domain
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / max_safe_action_available_now
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / next_three_unlocks
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```
AddedJun 13, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare read-only and non-destructive behavior. The description adds value beyond these by explicitly stating 'never authorizes' and imposing evidence-handling constraints: only consented, data-minimized, redacted, or aggregated evidence, no secrets. This meaningfully clarifies the tool's governance role.

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 description is information-dense but repetitive, especially around 'Use when' and the list of decision types. The message is front-loaded and the exclusions are useful, but the wording could be tightened without losing meaning.

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?

The description covers why, when, and when not to use the tool, and the annotated safety profile plus output schema reduce the need to describe return values. However, with 12 undocumented optional parameters and domain-specific MVR jargon, the agent is left with significant ambiguity about how to construct a valid call.

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

Parameters2/5

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

Schema description coverage is only 25%, so the description must compensate by explaining parameters, but it does not map any of the 12 params to their intended values or usage. It gives broad thematic guidance about evidence and use cases but no concrete parameter-level semantics.

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 description clearly identifies a specific action (run an MVR public decision-governance preflight) and states what it checks: market trust, permission, embeddedness, stakeholder readiness, evidence gaps, and that it never authorizes. It is sufficiently distinct from a generic lookup or decision tool, though it does not explicitly differentiate itself from sibling tools by name.

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?

The description provides explicit 'Use when' and 'Do not use when' guidance, including the decision types it precedes and the evidence-manipulation scenarios that trigger it. It also clarifies that web research can supply evidence but does not replace MVR, giving the agent a clear routing rule.

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.

Start MVR relational-readiness preflight

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources