a2a2p — Agent-to-Agent-to-Physical

co_invent_start_pass

Needs the signed-in link https://a2a2p.com/co-invent/mcp. On this public link it answers with how your person connects it. Older name for co_invent_begin_pass, kept so a connector with a saved tool list keeps working. Run an invention pass: give the idea in one sentence and Co-Invent takes it from brainstorm to a finished invention package (and, for the owner, a marketplace listing). Returns a pass_id; follow it with co_invent_pass_status. While you research what to invent, gather evidence: papers, standards, filings and product pages, each with the one-line claim it supports (and, where it proves one, the brief fact: landscape, hard, buyer, price or incumbents), and pass up to 12 as evidence when you start; Debbie weighs it first. To invent something end to end, call co_invent_begin_pass with the idea in one sentence and your evidence. Then call co_invent_pass_status with the pass_id it gives you, wait_seconds 20, again and again. Each answer has next. When next.needsAgent is true, you decide, as the person would in the app: read what next shows (the questions, every brainstormed idea, the full shortlist, the must-dos, each round's verdict), then call co_invent_act with next.operation and a body you build (next.example shows the shape). When next.operation is set and needsAgent is false, send it as it is. When it is null, check again. Read any part with co_invent_read, and say anything to the team at any step with co_invent_pass_say. At the end, rate the package; the owner's passes publish with co_invent_publish. A full pass usually takes 30 to 60 minutes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "idea": "<idea>"
    },
    "name": "co_invent_start_pass"
  }
}

Input Schema

Name	Required	Description
`who`	No	Who has the problem (optional).
`why`	No	Why it matters, in the person's words (optional).
`goal`	No	sell (the default) or self.
`idea`	Yes	The idea, or the problem it solves, in a sentence or two.
`evidence`	No	The evidence you gathered while researching what to invent: up to 12 items, each a public https link or a file, with the one-line claim it supports. Debbie weighs it first, and the certificate lists it as supplied by the inventor's agent.
`pivot_of`	No	When a finished pass missed the listing gate: its pass_id, to pivot once to a narrower sub-problem in the same field. A second miss drops the brief.
`constraints`	No	Anything it must or mustn't do (optional).
`for_marketplace`	No	Owner only: make it in the marketplace vault so it can be listed. On by default for the owner.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 6, 2026

changedInput schema / properties / evidence / description

Previous value: -"The evidence you gathered while researching what to invent: up to 8 items, each a public https link or a file, with the one-line claim it supports. Debbie weighs it first, and the certificate lists it as supplied by the inventor's agent."New value: +"The evidence you gathered while researching what to invent: up to 12 items, each a public https link or a file, with the one-line claim it supports. Debbie weighs it first, and the certificate lists it as supplied by the inventor's agent."

addedInput schema / properties / evidence / items / properties / fact

Added value: +{
+  "description": "The brief fact this item proves (optional): landscape (what's already filed and sold), hard (the hard sub-problem as a measurable spec), buyer (the named buyer), price (target unit price and parts-cost ceiling) or incumbents (named incumbents and what they don't do). Debbie's brief fills that fact from the item's claim and quote.",
+  "type": "string"
+}

changedInput schema / properties / evidence / maxItems
```
Previous value: -8New value: +12
```

Changed1 schema field changedNov 5, 2026

addedInput schema / properties / pivot_of

Added value: +{
+  "description": "When a finished pass missed the listing gate: its pass_id, to pivot once to a narrower sub-problem in the same field. A second miss drops the brief.",
+  "type": "string"
+}

Changed1 schema field changedNov 5, 2026

addedInput schema / properties / evidence

Added value: +{
+  "description": "The evidence you gathered while researching what to invent: up to 8 items, each a public https link or a file, with the one-line claim it supports. Debbie weighs it first, and the certificate lists it as supplied by the inventor's agent.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "claim": {
+        "description": "The one-line claim this item supports.",
+        "type": "string"
+      },
+      "date": {
+        "description": "When it was published (optional).",
+        "type": "string"
+      },
+      "file": {
+        "additionalProperties": false,
+        "description": "A file instead of a link: an image (JPEG, PNG, WebP), PDF, Word document or text, up to 10 MB.",
+        "properties": {
+          "base64": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "base64"
+        ],
+        "type": "object"
+      },
+      "quote": {
+        "description": "The exact words in it that support the claim (optional).",
+        "type": "string"
+      },
+      "url": {
+        "description": "A public https link: a paper, journal article, standard, filing or product page.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "claim"
+    ],
+    "type": "object"
+  },
+  "maxItems": 8,
+  "type": "array"
+}

AddedNov 5, 2026

TDQS

B3.4/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and does disclose meaningful traits: it returns a pass_id, typical duration of 30-60 minutes, evidence is weighed by Debbie first, and owner passes can publish to the marketplace. It never explicitly states that behavior is identical to co_invent_begin_pass, which is the key behavioral fact for an alias.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is bloated with a multi-step workflow tutorial (poll with wait_seconds 20, next.needsAgent, co_invent_act, co_invent_read, co_invent_pass_say, co_invent_publish) that belongs to co_invent_begin_pass, not to an alias. The actual alias explanation is one sentence buried in the middle, and the link/auth line is front-loaded but unexplained.

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?

An output schema exists, so return values need not be explained, and the description gives a pass_id hint and pacing. But for an 8-parameter tool it omits the most important fact for an agent deciding how to use it: whether this alias is fully equivalent to co_invent_begin_pass or differs in any way. The rest is workflow that duplicates a sibling.

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%, so the schema already explains idea, evidence, goal, pivot_of and for_marketplace. The description only restates a few of these (one-sentence idea, up to 12 evidence items weighed first) without adding format or syntax detail. 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 states this is the "older name for co_invent_begin_pass, kept so a connector with a saved tool list keeps working" and that it runs an invention pass from a one-sentence idea. That is a specific verb+resource and it distinguishes the tool from its canonical sibling. It is muddied because most of the remaining text describes co_invent_begin_pass rather than this tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implicit guidance exists: keep using this alias if a connector has a saved tool list, otherwise call co_invent_begin_pass. However, it then instructs the agent to "call co_invent_begin_pass" for end-to-end work, which leaves the when-to-use-this-tool condition (alias/compatibility) buried rather than stated up front.

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 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.