MVR API - Minimum Viable Relationships

Resolve the venture and market

mvr_entity_resolve

Read-only

Use when a startup, venture, programme, company, partner, or market actor must be resolved to a country, sector, and archetype before relational-readiness evidence is assessed. Use when: Use immediately after mvr_first_call when the user gives a company, venture, sector, country, or ambiguous market actor name, so the subject and target geography are resolved before evidence is assessed. Do not use when: Do not use as a readiness verdict or for unrelated entity lookup. Never submit secrets, personal identifiers, raw private interviews, or confidential evidence.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`payload`	Yes	Entity and market context to canonicalize before evidence assessment.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	No
`warning`	No
`next_steps`	No
`workflow_id`	No
`mcp_next_call`	No
`mcp_next_tool`	No
`response_meta`	No
`workflow_status`	No
`canonical_entity`	No
`workflow_expires_at`	No
`mvr_response_receipt`	No
`required_user_inputs`	No
`continuation_disposition`	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"
+}

Changed3 schema fields changedJul 12, 2026

changedInput schema / properties / payload / description

Previous value: -"Entity-resolution request body."New value: +"Entity and market context to canonicalize before evidence assessment."

addedInput schema / properties / payload / minProperties
```
Added value: +1
```

addedInput schema / properties / payload / properties

Added value: +{
+  "country": {
+    "description": "ISO country code or country name when known.",
+    "type": "string"
+  },
+  "entity_archetype": {
+    "description": "Known MVR archetype, if already identified.",
+    "type": "string"
+  },
+  "entity_name": {
+    "description": "Venture, company, market actor, or hypothetical entity name.",
+    "type": "string"
+  },
+  "market_scope": {
+    "additionalProperties": true,
+    "description": "Target geography for the proposed decision.",
+    "properties": {
+      "city": {
+        "type": "string"
+      },
+      "corridor": {
+        "type": "string"
+      },
+      "country": {
+        "type": "string"
+      },
+      "region": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "organization_type": {
+    "description": "Founder, SME, corporate, investor, institution, or other operator type when relevant.",
+    "type": "string"
+  },
+  "query": {
+    "description": "Free-text entity description when no stable name exists.",
+    "type": "string"
+  },
+  "sector": {
+    "description": "Sector or operating category when known.",
+    "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": {
+    "canonical_entity": {
+      "type": "object"
+    },
+    "response_meta": {
+      "type": "object"
+    },
+    "status": {
+      "type": "string"
+    },
+    "warning": {
+      "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 mark the operation as read-only and non-destructive. The description goes beyond this by adding a data-sensitivity constraint: never submit secrets, personal identifiers, raw private interviews, or confidential evidence. It also implies the tool handles ambiguous market actor names, which is useful behavioral context. 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.

Conciseness4/5

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

The description is organized with clear 'Use when' and 'Do not use when' sections, making it easy to scan and front-loaded with the core purpose. There is mild redundancy: the opening sentence restates the 'Use when' scenario that the following 'Use when' section repeats. Still, every part contributes to routing and safety.

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

Completeness4/5

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

For a read-only entity resolution tool with a nested payload and an output schema, the description covers workflow placement, exclusions, and input safety. The schema fills parameter details, and the output schema covers return values. The one minor gap is lack of explicit guidance on how market_scope interacts with the resolution outcome, but this is partially implied by 'target geography' and the schema.

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 coverage is 100%, with every parameter inside the payload having its own description. The tool description adds high-level context about when to provide inputs (e.g., right after first call) but does not add per-parameter meaning beyond the schema. Baseline 3 is appropriate because the schema already carries the semantic load.

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 action: resolve a startup, venture, programme, company, partner, or market actor to a country, sector, and archetype. It explicitly places the tool in the workflow between mvr_first_call and evidence assessment, and distinguishes it from siblings by excluding readiness verdicts and unrelated entity lookup.

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 gives an explicit 'Use when' trigger ('immediately after mvr_first_call when the user gives a company, venture, sector, country, or ambiguous market actor name'), a 'Do not use when' exclusion ('not as a readiness verdict or for unrelated entity lookup'), and a data-handling restriction. This fully routes the agent to the correct tool without ambiguity.

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.

Resolve the venture and market

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources