Skip to main content
Glama

a2a2p — Agent-to-Agent-to-Physical

by com.a2a2p
OverviewDiscussionsAdmin

render_supplier_email_binding

Render the caller's requirement as a reviewable RFC 5322 supplier-email draft after rebuilding its canonical supplier package and repeating quote-stage screening. The plain-language draft offers optional Can quote / Need changes / Decline reply choices and asks for price basis, freight scope, and lead-time basis when quoting. Suppliers may still reply in normal prose. Only an allow verdict renders. The operation validates one explicit recipient and an accountable sender-domain envelope, but cannot verify SPF, DKIM, or DMARC and therefore returns sendable=false. An explicit specification.assembly with two or more parts returns decomposition_required before file inspection or rendering. It is a stateless artifact transformation only: it stores nothing, sends nothing, contacts no supplier or provider, and grants no 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.
email_bindingYesExplicit envelope for a reviewable, non-sending RFC 5322 draft. No address is looked up or inferred.
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
statusYes
versionYes
artifactYes
contractYes
sendableYes
authorityYes
provenanceYes
conformanceYes
binding_sha256Yes
digest_semanticsYes
sender_authenticationYes
reply_route_verificationYes
requirements_before_sendingYes

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
    • changedOutput schema / properties / version / const
      Previous value: -"1.2.0"New value: +"1.3.0"
  3. 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"
+]
  4. Changed1 schema field changed
    • changedOutput schema / properties / version / const
      Previous value: -"1.1.0"New value: +"1.2.0"
  5. 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"
+}
  6. 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"
  7. Changed3 schema fields changed
    • addedInput schema / properties / email_binding / allOf
      Added value: +[
+  {
+    "if": {
+      "properties": {
+        "principal_kind": {
+          "const": "organization"
+        }
+      },
+      "required": [
+        "principal_kind"
+      ]
+    },
+    "then": {
+      "required": [
+        "principal_registered_address"
+      ]
+    }
+  }
+]
    • addedInput schema / properties / email_binding / properties / principal_registered_address
      Added value: +{
+  "description": "Required when principal_kind is organization.",
+  "maxLength": 500,
+  "minLength": 1,
+  "type": "string"
+}
    • changedOutput schema / properties / version / const
      Previous value: -"1.0.0"New value: +"1.1.0"
  8. Added

TDQS

A4.3/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 discloses that it cannot verify SPF/DKIM/DMARC and therefore always returns sendable=false, that it is a stateless artifact transformation that stores nothing, sends nothing, contacts no supplier, and grants no quote/order/payment/fabrication authority. It also discloses the decomposition_required early-return path. This is exactly the behavioral context an agent needs and cannot 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 purpose and every sentence carries substantive information. It is a dense single block of long sentences, though, and could be broken up for faster scanning; nothing is filler, but readability suffers slightly.

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, 12-parameter, nested-object tool with an output schema present, the description covers what the draft contains (reply choices, requested bases), the gating verdict, the decomposition path, and the safety/authority profile. Since an output schema exists, return-value detail is not needed, and nothing an agent needs to call it correctly is missing.

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 the schema already documents the 12 parameters and the baseline would be 3. The description still adds meaning: it explains that the operation validates one explicit recipient and an accountable sender-domain envelope, and that quoting drafts request price basis, freight scope, and lead-time basis — context that informs how the email_binding and intent fields are used.

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+resource: render the caller's requirement as a reviewable RFC 5322 supplier-email draft, after rebuilding the supplier package and repeating quote screening. It is clearly a draft-rendering artifact operation, but it never names the sibling it is distinguished from (e.g. build_supplier_request_package), so an agent must infer the boundary.

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 real gating conditions: only an allow verdict renders, and an explicit specification.assembly with two or more parts returns decomposition_required before file inspection or rendering. This tells the agent when the call will and will not succeed, though it does not explicitly route to alternative siblings for filtered cases.

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