Bounded footwear fit checks for a specific shoe, person, and intended use.
Scored across 1 tool
There is only one tool, so there is no possibility of misselection or overlap with a sibling. Its description also clearly states inclusion criteria and explicit exclusions (education, style, conversion, medical advice).
The single name check_footwear_fit follows a clean verb_noun snake_case convention with no competing styles to conflict with. Nothing in the set deviates from the pattern.
A one-tool server is borderline thin for a domain that involves product, person, and use-context inputs plus follow-ups such as alternatives or record-keeping. The lone tool is rich and non-trivial, but the surface offers no companion operations.
The tool covers the core bounded fit judgment well, including decision, unknowns, next steps, and alternatives. However, there is no supporting surface for product lookup, prior-fit history, or follow-up actions beyond what a single judgment call returns.
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.
| Name | Required | Description | Default |
|---|---|---|---|
| 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 |
| Name | Required | Description |
|---|---|---|
| why | Yes | |
| boundary | No | |
| decision | Yes | |
| unknowns | Yes | |
| nextSteps | Yes | |
| provenance | No | |
| alternatives | No | |
| coreJudgment | No | |
| currentAssessment | Yes |
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.
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.
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.
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.
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.
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.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
check_footwear_fit7 fields changedInput schema / properties / canonicalRequestAdded 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"
+}Output schema / $defs / CoreJudgmentAdded 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"
+}Output schema / $defs / Provenance / properties / adapterMode / constRemoved value: -"PROTOTYPE_RULES"Output schema / $defs / Provenance / properties / adapterMode / enumAdded value: +[
+ "PROTOTYPE_RULES",
+ "CANONICAL_CORE"
+]Output schema / $defs / Provenance / properties / canonicalCoreExecuted / constRemoved value: -falseOutput schema / $defs / Provenance / properties / coreBaseline / constRemoved value: -"phase-1-approved-baseline@7da520058257362a35c88173c3cd03d37c8965c8"Output schema / properties / coreJudgmentAdded value: +{
+ "anyOf": [
+ {
+ "$ref": "#/$defs/CoreJudgment"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null
+}check_footwear_fitFree, read-only truck and Jeep parts fitment: what fits your vehicle, fit checks, tire sizes.
Owner-side infrastructure project development intake with fit check before authorized submission.
Neutral cross-brand bra-size translation and a live in-stock bra catalog by size.
Deterministic fitness calculators — TDEE, adaptive TDEE, body fat, 1RM, macros — with consensus.
Add one secure layer between your agents and this server.
