Shoe Fit Checker

Check footwear fit

check_footwear_fit

Read-onlyIdempotent

Use when the user needs a bounded fit judgment about whether a specific finished footwear product is likely to work for a specific person in a stated use context, including pressure, toe contact, heel slip, width/size questions, dynamic-use problems, keep/exchange decisions, and fit-driven alternatives. Do not use for generic shoe education, style advice, simple size conversion, or medical diagnosis/treatment. When presenting a returned fit judgment, preserve the tool's decision, unknowns, next steps, alternatives, professional boundary, evidence state, and execution provenance. When coreJudgment is present, preserve its primaryState, reasonCodes, criticalUnknownIds, Case/Rule Set identity, and do not replace them with stronger host conclusions. Do not add or strengthen unverified product facts, gait or biomechanical labels, medical causal explanations or diagnoses, or extra size/width/lacing/product prescriptions unless they were independently established as verified evidence in the request. Keep any separately sourced external information clearly separate from the bounded fit judgment.

Input Schema

TableJSON Schema

Name	Required	Description
`product`	Yes
`evidence`	No
`question`	Yes
`useContext`	No
`bodySignals`	No
`canonicalRequest`	No	Optional complete governed Match & Fit Core JudgmentRequest. It is passed through without semantic field invention and is canonical only if the configured Core executor validates and executes it.
`interactionSignals`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`why`	Yes
`boundary`	No
`decision`	Yes
`unknowns`	Yes
`nextSteps`	Yes
`provenance`	No
`alternatives`	No
`coreJudgment`	No
`currentAssessment`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 1, 2026

addedInput schema / properties / canonicalRequest

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional complete governed Match & Fit Core JudgmentRequest. It is passed through without semantic field invention and is canonical only if the configured Core executor validates and executes it.",
+  "title": "Canonicalrequest"
+}

addedOutput schema / $defs / CoreJudgment

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "caseId": {
+      "title": "Caseid",
+      "type": "string"
+    },
+    "caseVersion": {
+      "title": "Caseversion",
+      "type": "string"
+    },
+    "criticalUnknownIds": {
+      "items": {
+        "type": "string"
+      },
+      "title": "Criticalunknownids",
+      "type": "array"
+    },
+    "executionId": {
+      "title": "Executionid",
+      "type": "string"
+    },
+    "packageId": {
+      "title": "Packageid",
+      "type": "string"
+    },
+    "primaryState": {
+      "title": "Primarystate",
+      "type": "string"
+    },
+    "reasonCodes": {
+      "items": {
+        "type": "string"
+      },
+      "title": "Reasoncodes",
+      "type": "array"
+    },
+    "ruleSetId": {
+      "title": "Rulesetid",
+      "type": "string"
+    },
+    "ruleSetVersion": {
+      "title": "Rulesetversion",
+      "type": "string"
+    }
+  },
+  "required": [
+    "primaryState",
+    "reasonCodes",
+    "criticalUnknownIds",
+    "packageId",
+    "executionId",
+    "caseId",
+    "caseVersion",
+    "ruleSetId",
+    "ruleSetVersion"
+  ],
+  "title": "CoreJudgment",
+  "type": "object"
+}

removedOutput schema / $defs / Provenance / properties / adapterMode / const
```
Removed value: -"PROTOTYPE_RULES"
```
addedOutput schema / $defs / Provenance / properties / adapterMode / enum
```
Added value: +[
+  "PROTOTYPE_RULES",
+  "CANONICAL_CORE"
+]
```
removedOutput schema / $defs / Provenance / properties / canonicalCoreExecuted / const
```
Removed value: -false
```

removedOutput schema / $defs / Provenance / properties / coreBaseline / const

Removed value: -"phase-1-approved-baseline@7da520058257362a35c88173c3cd03d37c8965c8"

addedOutput schema / properties / coreJudgment

Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/CoreJudgment"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

First observedSep 15, 2026

TDQS

A4.2/5.0

Behavior5/5

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

The annotations already cover read-only, idempotent, non-destructive, closed-world behavior. The description adds substantial behavioral context beyond annotations: how to present the returned fit judgment, which fields to preserve (decision, unknowns, next steps, alternatives, professional boundary, evidence state, execution provenance), and prohibitions on strengthening unverified claims or adding unsupported medical, biomechanical, or product prescriptions.

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 front-loaded with usage guidance, which is good. However, it is a single dense paragraph with repetitive preservation instructions (e.g., repeated 'preserve' directives and multiple 'do not' clauses) that could be more structurally concise 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 tool has an output schema, so return values need not be explained, and annotations cover the safety profile. Usage and output-integrity guidance are strong, but with 7 parameters and only 14% schema coverage, the description leaves input parameter semantics largely unexplained, making it incomplete for correct invocation.

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 14% across 7 parameters, so the description must compensate, but it does not explain parameter names, types, allowed values, or formats. It alludes to use context and body signals conceptually but provides no mapping to the actual input fields such as evidence, bodySignals, interactionSignals, or canonicalRequest.

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: a bounded fit judgment about whether a specific finished footwear product will work for a specific person in a stated use context. It gives concrete scope examples (pressure, toe contact, heel slip, width/size questions, keep/exchange decisions) that clearly distinguish it from generic shoe education, style advice, size conversion, and medical diagnosis.

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?

It explicitly lists when to use the tool and when not to use it, covering both positive triggers and clear exclusions. No alternative sibling tool exists to name, so the when/when-not guidance is complete for routing.

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

All Shoe Fit Checker 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?