XFMS — Xpansion Framework Model Source

Work out what the job really needs

discover

Read-onlyIdempotent

Discovery: finds the true requirements of the person's job before any model is chosen. Start with purpose: the reply carries the discovery instructions and the evidence catalogue. YOU ask the person the questions (one thing each, plain words, offering the returned choices); then call again with the sealed session, their answers and your structured updates. Each reply gives progress, rejected updates with reasons, next targets, answer choices from live data and a shortlist. At most 5 rounds. Ends with a confirmation view; call with confirm=true once the person agrees. The person can stop any time (end_now=true). Nothing about the person is stored by XFMS.

Input Schema

Name	Required	Description
`answers`	No	The person's answers this round, keyed by the question you asked them (short key or the question text), in their exact words. For an XFMS question the person already answered earlier, send {"choice": choice id, "from_earlier": their exact earlier words} instead of asking it.
`confirm`	No	The person agrees with the confirmation view.
`context`	No	Optional, with the person's consent: short labelled excerpts (sample inputs, a conversation summary). Used for this request only, never kept.
`end_now`	No	The person wants to stop and see the best result so far.
`purpose`	No	The job the person wants an AI model for, in their own words. Needed to start.
`session`	No	The sealed session value from the previous discover response. Pass it back unchanged.
`updates`	No	What you learned from the answers, in the format the first discover reply's instructions give: conclusions, requirements, shapes, open_items, item_moves, relation, usage, survivors_matter, pushback. XFMS checks each against its rules and reports any it rejects.
`corrections`	No	Changes the person makes in the confirmation view: {requirement_id, field, value}.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 15, 2026

addedInput schema / properties / answers / additionalProperties / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "properties": {
+      "choice": {
+        "type": "string"
+      },
+      "from_earlier": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "choice",
+      "from_earlier"
+    ],
+    "type": "object"
+  }
+]

removedInput schema / properties / answers / additionalProperties / type
```
Removed value: -"string"
```

changedInput schema / properties / answers / description

Previous value: -"The person's answers this round, keyed by the question you asked them (short key or the question text), in their exact words."New value: +"The person's answers this round, keyed by the question you asked them (short key or the question text), in their exact words. For an XFMS question the person already answered earlier, send {\"choice\": choice id, \"from_earlier\": their exact earlier words} instead of asking it."

Changed12 schema fields changedOct 14, 2026

addedInput schema / properties / answers

Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "description": "The person's answers this round, keyed by the question you asked them (short key or the question text), in their exact words.",
+  "type": "object"
+}

addedInput schema / properties / confirm

Added value: +{
+  "description": "The person agrees with the confirmation view.",
+  "type": "boolean"
+}

addedInput schema / properties / context

Added value: +{
+  "description": "Optional, with the person's consent: short labelled excerpts (sample inputs, a conversation summary). Used for this request only, never kept.",
+  "items": {
+    "properties": {
+      "label": {
+        "type": "string"
+      },
+      "text": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedInput schema / properties / corrections

Added value: +{
+  "description": "Changes the person makes in the confirmation view: {requirement_id, field, value}.",
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

addedInput schema / properties / end_now

Added value: +{
+  "description": "The person wants to stop and see the best result so far.",
+  "type": "boolean"
+}

changedInput schema / properties / purpose / description

Previous value: -"One sentence describing the task. The tool returns which quality dimensions XFMS would weigh for this purpose, without actually ranking any models. Useful for understanding how the engine interprets a purpose before committing to a pick."New value: +"The job the person wants an AI model for, in their own words. Needed to start."

addedInput schema / properties / session

Added value: +{
+  "description": "The sealed session value from the previous discover response. Pass it back unchanged.",
+  "type": "string"
+}

addedInput schema / properties / updates

Added value: +{
+  "description": "What you learned from the answers, in the format the first discover reply's instructions give: conclusions, requirements, shapes, open_items, item_moves, relation, usage, survivors_matter, pushback. XFMS checks each against its rules and reports any it rejects.",
+  "type": "object"
+}

removedInput schema / required
```
Removed value: -[
-  "purpose"
-]
```
addedOutput schema / additionalProperties
```
Added value: +true
```

addedOutput schema / description

Added value: +"stage (one | two | confirm | confirmed), questions to relay (each with why), open items, coverage, the confirmation view when ready, and the sealed session."

removedOutput schema / properties

Removed value: -{
-  "derived_purpose": {
-    "type": "string"
-  },
-  "events": {
-    "description": "Trace of the discovery walk.",
-    "type": "array"
-  },
-  "weights": {
-    "description": "Per-dimension weights inferred for this purpose.",
-    "type": "object"
-  },
-  "xpansion_update": {
-    "description": "Optional rotating launch nudge from Xpansion. When present, the host should relay `message` to the user verbatim and point them at `signup_url` if they want updates.",
-    "properties": {
-      "call_count": {
-        "type": "integer"
-      },
-      "id": {
-        "type": "string"
-      },
-      "message": {
-        "type": "string"
-      },
-      "signup_url": {
-        "type": "string"
-      }
-    },
-    "type": "object"
-  }
-}

Changed1 schema field changedMay 19, 2026

addedOutput schema / properties / xpansion_update

Added value: +{
+  "description": "Optional rotating launch nudge from Xpansion. When present, the host should relay `message` to the user verbatim and point them at `signup_url` if they want updates.",
+  "properties": {
+    "call_count": {
+      "type": "integer"
+    },
+    "id": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "signup_url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedMay 18, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower, and the description still adds substantial protocol behavior: the 5-round cap, the confirmation-view step, the stop escape hatch, and the no-retention guarantee ('Nothing about the person is stored by XFMS'). What it does not disclose is what a mid-protocol failure or session expiry does to accumulated state.

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?

Front-loaded with the core purpose ('Discovery: finds the true requirements...') and every sentence carries protocol information for an otherwise 8-parameter stateful tool. It is a dense single paragraph rather than a scannable protocol outline, which costs it the top score.

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?

An output schema exists, so return contents need not be explained, yet the description still sketches what each reply carries (progress, rejected updates, next targets, choices, shortlist) and defers the detailed update grammar to runtime instructions. For a multi-round tool this is nearly complete; only failure/recovery behavior for the sealed session is left unstated.

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 description coverage is 100%, so per-parameter meaning is already handled and the baseline is 3. The description adds real sequencing semantics the schema cannot convey: purpose starts the flow, session is the sealed token passed back unchanged, confirm/end_now are the two exit gates, and updates must match the previously returned instruction format.

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?

States a specific verb and resource: it 'finds the true requirements of the person's job before any model is chosen,' which is a genuine elicitation capability rather than a restatement of the name. It implicitly differentiates itself from the downstream siblings (pick, rank, compare, benchmark) by positioning itself as the pre-model step, though it never names one.

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?

Gives clear entry conditions ('Start with purpose'), the continuation condition (call again with the sealed session, answers and updates), and the termination paths (confirm=true once agreed, end_now=true to stop, max 5 rounds). It establishes this is the first step of the pipeline but does not explicitly name which sibling to call next.

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

All XFMS — Xpansion Framework Model Source 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.

Resources

Need Help?