Skip to main content
Glama

a2a2p — Agent-to-Agent-to-Physical

by com.a2a2p
OverviewDiscussionsAdmin

request_provider_estimate

Submit a requirement to the durably queued provider-estimate workflow without holding the connection open. Returns a quote_job_id in milliseconds; scheduled settlement runs outside request waitUntil. Scheduled provider contact is not active in this release and cannot be enabled by an environment flag, so admitted jobs currently terminate as degraded with a deterministic model estimate. Additive processes with an STL design file only, for now. The requirement is screened before storage; any future provider activation must also screen the exact file bytes before contact. Every admission result is machine-readable. Rejections carry a stable closed-set reason_code, retry boundary, required input, and deterministic next_action; admitted responses carry the same versioned admission contract. An explicit specification.assembly with two or more parts is rejected before job creation or provider contact and must be decomposed first. Estimate only — never a quote, order, payment, or fabrication commitment. Poll with check_quote_job until a terminal status: completed (provider figure), degraded (deterministic model estimate with the provider's absence explained), or refused (screening).

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.

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. Changed4 schema fields changed
    • changedInput schema / properties / specification / properties / design_files / description
      Previous value: -"STEP/STL/DXF file references."New value: +"Temporary or externally hosted manufacturing file references ({url, format, optional role}). Accepted upload aliases: stl, step, stp, dxf, pdf; shared downstream ceiling: 8388608 bytes."
    • addedInput schema / properties / specification / properties / design_files / items / properties / format / enum
      Added value: +[
+  "stl",
+  "step",
+  "stp",
+  "dxf",
+  "pdf"
+]
    • addedInput schema / properties / specification / properties / design_files / items / properties / role
      Added value: +{
+  "enum": [
+    "geometry",
+    "drawing",
+    "reference"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / specification / properties / design_files / items / required
      Added value: +[
+  "url",
+  "format"
+]
  6. Added

TDQS

A4.4/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 discharges it: durable queueing without holding the connection, millisecond return of quote_job_id, settlement outside request waitUntil, screening before storage, the current degraded-mode behavior of admitted jobs, and the machine-readable closed-set rejection contract. This is behavior an agent could not get from structured fields.

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 action (submit, returns quote_job_id in ms) and well organized, but it is dense and long; several clauses about admission contracts and screening could be tightened. Every sentence still carries distinct information useful to invocation.

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

Completeness5/5

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

For a complex 11-parameter tool with no output schema, the description supplies the return contract (quote_job_id, terminal statuses completed/degraded/refused) and the degradation/screening behavior, leaving no major gap an agent needs before calling it.

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%, so the schema already documents all 11 parameters (requirement/intent layering, specification fields, design_files, etc.). The description mentions requirement, specification.assembly, and the STL design-file constraint but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb (submit) and resource (requirement to the queued provider-estimate workflow), and sharply bounds it: 'Estimate only — never a quote, order, payment, or fabrication commitment.' This differentiates it from siblings like request_physical_solution and get_supply_options without needing their schemas.

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 concrete conditions — additive processes with an STL design file only, single-part (explicit specification.assembly with 2+ parts rejected) — and routes the agent to check_quote_job for polling terminal statuses. It stops short of explicitly contrasting with the other request/explore siblings, but the scope constraints are unusually clear.

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