Skip to main content
Glama

a2a2p — Agent-to-Agent-to-Physical

by com.a2a2p
OverviewDiscussionsAdmin

prepare_domain_solutioning_case

Prepare a synchronous, deterministic, privacy-minimized engineering case for a compatible domain-intelligence system. Use it when intake_classification is capability_concept or assembly_or_system and mechanism selection or decomposition is required, or when a complete single-part intent has no specifications and review offers the design_brief continuation. The case preserves requester facts, deterministic evidence, screening state, unknowns, and a versioned candidate-output contract while removing design-file URLs, bytes, contact fields, and callback routes. This operation does not call deb8stack or any model, choose a mechanism, validate a proposal, store a request, contact a supplier, or grant quote, order, payment, or fabrication authority.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
intentNoLayer 1 — the problem. What the physical matter needs to DO. Use this for intent-driven requests where the agent describes purpose and a2a2p recommends solutions.
contactNoOptional email or callback endpoint for quote delivery.
deadlineNoRequired delivery date or timeframe. Maps to intent.timeline.
quantityNoNumber of units needed. Maps to intent.quantity.
budget_usdNoApproximate budget in USD. Maps to intent.budget_envelope.
constraintsNoHard constraints: tolerances, certifications, materials to avoid, size/weight limits. Maps to intent.functional_requirements.
requirementNoPlain-language description of the physical need. Maps to intent.purpose. Include function, dimensions, materials, load/performance requirements, environment, and interfaces where known.
callback_urlNoOptional HTTPS URL. When the quote is ready, a2a2p POSTs it as JSON to this URL.
specificationNoLayer 2 — the solution. What the physical matter IS. Populate what is known. Precise specifications produce faster, tighter quotes. Controlled vocabularies are preferred but open values are accepted.
business_contextNoOptional business requirements (expected volumes, cost targets, ROI constraints). If provided, the quote includes a business case.
rejected_alternativesNoOptions already considered and ruled out. Prevents re-suggesting and builds the learning corpus.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nextYes
safetyYes
contractYes
authorityYes
activationYes
provenanceYes
case_digestYes
requirementYes
requested_workYes
expected_resultYes
contract_versionYes
deterministic_evidenceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / properties / intent / properties / alternates_acceptable
      Added value: +{
+  "description": "Whether a supplier may propose a different material, process or stock size.",
+  "type": [
+    "boolean",
+    "string"
+  ]
+}
    • addedInput schema / properties / intent / properties / inspection_documents
      Added value: +{
+  "description": "Inspection or material documents required with the parts, or \"none required\".",
+  "type": "string"
+}
    • addedInput schema / properties / intent / properties / quote_by
      Added value: +{
+  "description": "Date a quote is needed by.",
+  "type": "string"
+}
    • addedInput schema / properties / intent / properties / ship_to_region
      Added value: +{
+  "description": "Delivery region. When present, a supplier package asks for a price including freight to it; when absent, freight is excluded.",
+  "type": "string"
+}
    • addedInput schema / properties / specification / properties / cutting
      Added value: +{
+  "description": "Cutting-tool constraints for routed or milled profiles.",
+  "properties": {
+    "inside_corner_relief": {
+      "description": "dogbone or t_bone: the supplier adds that relief; in_file: relief is already drawn; not_required: tool-radius corners are acceptable.",
+      "enum": [
+        "dogbone",
+        "t_bone",
+        "in_file",
+        "not_required"
+      ],
+      "type": "string"
+    },
+    "tool_diameter_mm": {
+      "description": "Smallest cutter that will be used. Inside corners and holes with a smaller radius are flagged against the measured DXF.",
+      "exclusiveMinimum": 0,
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
    • addedInput schema / properties / specification / properties / notes
      Added value: +{
+  "description": "Manufacturing notes for the supplier. Carried verbatim into the supplier package; never parsed into facts. State anything a check must use in its structured field.",
+  "maxLength": 4000,
+  "type": "string"
+}
    • changedInput schema / properties / specification / properties / process / enum
      Previous value: -[
-  "cnc_milling",
-  "cnc_turning",
-  "fdm_3d_print",
-  "sla_3d_print",
-  "sls_3d_print",
-  "sheet_metal",
-  "laser_cutting",
-  "casting",
-  "injection_molding",
-  "extrusion"
-]New value: +[
+  "cnc_milling",
+  "cnc_turning",
+  "cnc_routing",
+  "fdm_3d_print",
+  "sla_3d_print",
+  "sls_3d_print",
+  "sheet_metal",
+  "laser_cutting",
+  "casting",
+  "injection_molding",
+  "extrusion"
+]
    • addedInput schema / properties / specification / properties / sheet_stock
      Added value: +{
+  "description": "The sheet a flat part is cut from. For plywood a supplier needs face_grade, nominal and actual thickness, ply_count and glue_class; for MDF, grade and thickness. Missing facts are asked, never chosen by a2a2p.",
+  "properties": {
+    "actual_thickness_mm": {
+      "anyOf": [
+        {
+          "exclusiveMinimum": 0,
+          "type": "number"
+        },
+        {
+          "properties": {
+            "max": {
+              "type": "number"
+            },
+            "min": {
+              "type": "number"
+            }
+          },
+          "type": "object"
+        }
+      ],
+      "description": "Measured or specified actual thickness. Stock-relative tolerances also satisfy this: the joint follows the sheet."
+    },
+    "face_grade": {
+      "description": "Face/back veneer grade, for example B/BB.",
+      "type": "string"
+    },
+    "glue_class": {
+      "description": "Bond class, for example EN 314-2 class 1 (interior) or class 3 (exterior).",
+      "type": "string"
+    },
+    "grade": {
+      "description": "Panel grade for MDF and similar boards, for example standard or moisture_resistant.",
+      "type": "string"
+    },
+    "grain_direction": {
+      "description": "Face-grain direction relative to the declared X/Y dimensions.",
+      "enum": [
+        "along_x",
+        "along_y",
+        "not_applicable"
+      ],
+      "type": "string"
+    },
+    "nominal_thickness_mm": {
+      "exclusiveMinimum": 0,
+      "type": "number"
+    },
+    "ply_count": {
+      "minimum": 1,
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}
    • addedInput schema / properties / specification / properties / tolerances
      Added value: +{
+  "additionalProperties": {
+    "anyOf": [
+      {
+        "exclusiveMinimum": 0,
+        "type": "number"
+      },
+      {
+        "properties": {
+          "allowance_mm": {
+            "description": "Added to the measured stock thickness; negative for an interference fit.",
+            "type": "number"
+          },
+          "fit_class": {
+            "description": "Optional label such as push_fit or press_fit.",
+            "type": "string"
+          },
+          "minus": {
+            "minimum": 0,
+            "type": "number"
+          },
+          "nominal": {
+            "exclusiveMinimum": 0,
+            "type": "number"
+          },
+          "plus": {
+            "minimum": 0,
+            "type": "number"
+          },
+          "relative_to": {
+            "enum": [
+              "measured_stock_thickness"
+            ],
+            "type": "string"
+          },
+          "unit": {
+            "type": "string"
+          },
+          "value": {
+            "exclusiveMinimum": 0,
+            "type": "number"
+          }
+        },
+        "type": "object"
+      }
+    ]
+  },
+  "description": "Exact numeric tolerance callouts keyed by feature. They govern over tolerance_class for the named feature. Forms: a positive number (plus or minus that amount); { nominal, plus, minus }; or a stock-relative rule { relative_to: \"measured_stock_thickness\", allowance_mm, plus, minus, fit_class } for joints cut to the sheet actually used.",
+  "type": "object"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / specification / properties / process / enum
      Previous value: -[
-  "cnc_milling",
-  "cnc_turning",
-  "fdm_3d_print",
-  "sla_3d_print",
-  "sls_3d_print",
-  "sheet_metal",
-  "casting",
-  "injection_molding",
-  "extrusion"
-]New value: +[
+  "cnc_milling",
+  "cnc_turning",
+  "fdm_3d_print",
+  "sla_3d_print",
+  "sls_3d_print",
+  "sheet_metal",
+  "laser_cutting",
+  "casting",
+  "injection_molding",
+  "extrusion"
+]
  3. Changed1 schema field changed
    • addedInput schema / properties / intent / properties / functional_requirements / properties / load_case / properties / allowable_shear_stress_mpa
      Added value: +{
+  "description": "Optional requester-supplied transverse-shear design allowable; evaluated independently and never inferred from handbook data.",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}
  4. Changed5 schema fields changed
    • changedInput schema / properties / intent / properties / purpose / description
      Previous value: -"What the physical matter needs to accomplish (one line minimum, required)."New value: +"What the physical matter needs to accomplish (one non-whitespace line minimum, required)."
    • addedInput schema / properties / intent / properties / purpose / minLength
      Added value: +1
    • addedInput schema / properties / intent / properties / purpose / pattern
      Added value: +"\\S"
    • addedInput schema / properties / requirement / minLength
      Added value: +1
    • addedInput schema / properties / requirement / pattern
      Added value: +"\\S"
  5. Changed27 schema fields changed
    • addedOutput schema / $defs / candidate / properties / evidence_refs / items / additionalProperties
      Added value: +true
    • addedOutput schema / $defs / candidate / properties / evidence_refs / items / properties
      Added value: +{
+  "kind": {
+    "maxLength": 5000,
+    "minLength": 1,
+    "type": "string"
+  },
+  "path": {
+    "maxLength": 5000,
+    "minLength": 1,
+    "type": "string"
+  }
+}
    • addedOutput schema / $defs / candidate / properties / evidence_refs / items / required
      Added value: +[
+  "kind",
+  "path"
+]
    • addedOutput schema / $defs / candidate / properties / evidence_refs / minItems
      Added value: +1
    • addedOutput schema / $defs / candidate / properties / functional_decomposition / items / additionalProperties
      Added value: +true
    • addedOutput schema / $defs / candidate / properties / functional_decomposition / items / properties
      Added value: +{
+  "function": {
+    "maxLength": 5000,
+    "minLength": 1,
+    "type": "string"
+  },
+  "part": {
+    "maxLength": 5000,
+    "minLength": 1,
+    "type": "string"
+  }
+}
    • addedOutput schema / $defs / candidate / properties / functional_decomposition / items / required
      Added value: +[
+  "function",
+  "part"
+]
    • addedOutput schema / $defs / candidate / properties / functional_decomposition / maxItems
      Added value: +100
    • addedOutput schema / $defs / candidate / properties / rejected_alternatives / items / additionalProperties
      Added value: +true
    • addedOutput schema / $defs / candidate / properties / rejected_alternatives / items / properties
      Added value: +{
+  "mechanism": {
+    "maxLength": 5000,
+    "minLength": 1,
+    "type": "string"
+  },
+  "reason": {
+    "maxLength": 5000,
+    "minLength": 1,
+    "type": "string"
+  }
+}
    • addedOutput schema / $defs / candidate / properties / rejected_alternatives / items / required
      Added value: +[
+  "mechanism",
+  "reason"
+]
    • addedOutput schema / $defs / candidate / properties / tradeoffs / items / additionalProperties
      Added value: +true
    • addedOutput schema / $defs / candidate / properties / tradeoffs / items / properties
      Added value: +{
+  "benefit": {
+    "maxLength": 5000,
+    "minLength": 1,
+    "type": "string"
+  },
+  "choice": {
+    "maxLength": 5000,
+    "minLength": 1,
+    "type": "string"
+  },
+  "cost": {
+    "maxLength": 5000,
+    "minLength": 1,
+    "type": "string"
+  }
+}
    • addedOutput schema / $defs / candidate / properties / tradeoffs / items / required
      Added value: +[
+  "choice",
+  "benefit",
+  "cost"
+]
    • addedOutput schema / $defs / candidate / properties / validation_plan / items / additionalProperties
      Added value: +true
    • addedOutput schema / $defs / candidate / properties / validation_plan / items / properties
      Added value: +{
+  "criterion": {
+    "maxLength": 5000,
+    "minLength": 1,
+    "type": "string"
+  },
+  "test": {
+    "maxLength": 5000,
+    "minLength": 1,
+    "type": "string"
+  }
+}
    • addedOutput schema / $defs / candidate / properties / validation_plan / items / required
      Added value: +[
+  "test",
+  "criterion"
+]
    • changedOutput schema / $defs / result / properties / contract_version / const
      Previous value: -"0.2.0-draft"New value: +"0.3.0-draft"
    • addedOutput schema / $defs / result / properties / dissent / items / additionalProperties
      Added value: +true
    • addedOutput schema / $defs / result / properties / dissent / items / properties
      Added value: +{
+  "candidate_id": {
+    "maxLength": 5000,
+    "minLength": 1,
+    "type": "string"
+  },
+  "concern": {
+    "maxLength": 5000,
+    "minLength": 1,
+    "type": "string"
+  }
+}
    • addedOutput schema / $defs / result / properties / dissent / items / required
      Added value: +[
+  "candidate_id",
+  "concern"
+]
    • addedOutput schema / $defs / result / properties / dissent / maxItems
      Added value: +100
    • addedOutput schema / $defs / result / properties / recommendation / properties / overturn_if / items / maxLength
      Added value: +5000
    • addedOutput schema / $defs / result / properties / recommendation / properties / overturn_if / items / minLength
      Added value: +1
    • addedOutput schema / $defs / result / properties / recommendation / properties / overturn_if / items / type
      Added value: +"string"
    • changedOutput schema / contract_version
      Previous value: -"0.2.0-draft"New value: +"0.3.0-draft"
    • changedOutput schema / properties / contract_version / const
      Previous value: -"0.2.0-draft"New value: +"0.3.0-draft"
  6. Added

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so richly: it declares synchrony and determinism, specifies exactly what data is preserved (requester facts, evidence, screening state, unknowns, versioned contract) and what is stripped (design-file URLs, bytes, contact fields, callback routes), and enumerates the side effects it does not perform (no model call, no storage, no supplier contact, no quote/order authority). This is far beyond what a schema could convey.

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?

Purpose and trigger conditions are front-loaded in the first two sentences, and the closing negative clause, while long, earns its place by fencing off sibling operations. The prose is dense and jargon-heavy ('design_brief continuation', 'deb8stack') but not redundant.

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-value documentation is unnecessary, and schema coverage is complete. The description covers behavior, data handling and invocation gating adequately; its only gap is that several gating terms (intake_classification, design_brief continuation) reference vocabulary defined outside this tool.

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 description coverage is 100% across 11 parameters, so the schema already documents every field and its nesting in detail. The description adds no parameter-level semantics (no syntax, defaults, or interaction rules such as intent vs requirement precedence), so the baseline 3 applies.

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 gives a specific verb and resource ('Prepare a ... engineering case for a compatible domain-intelligence system') and qualifies it with synchronous/deterministic/privacy-minimized. It never names a sibling outright, but the explicit negative scope (does not call deb8stack, choose a mechanism, validate a proposal, store a request) implicitly separates it from validate_domain_solutioning_result, request_physical_solution and review_specification.

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?

It states concrete triggering conditions: 'Use it when intake_classification is capability_concept or assembly_or_system and mechanism selection or decomposition is required, or when a complete single-part intent has no specifications and review offers the design_brief continuation.' That is clear when-to-use guidance, but no alternative tool is named for the negative case, so the agent must infer what to use otherwise.

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

All a2a2p — Agent-to-Agent-to-Physical toolsInspect
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