Skip to main content
Glama

a2a2p — Agent-to-Agent-to-Physical

co_invent_pass_read

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_read, kept so a connector with a saved tool list keeps working. Read any part of a pass, as a person reads it in the app. part: list (what's there), brief, shortlist, concept, brainstorm, review, mustdos, requirements, spec, bom, risks, business, market, engineering, diagrams, patent, claimcheck, rounds, app, checks, provenance, activity, debbie, attribution, commons (a2a2p's claims repository search: prior art found while reading, unpublished Invention Commons listings kept as precedence risks with their listing dates, and the package's notices of Commons inventions whose claims may overlap the drafted claims, by public teaser only) or reading (the reading step's ranked list of everything in the idea and its attachments, function and mechanism first, each item with its source, and how many of each attachment's items reached the brainstorm, design, concepts, shortlist, requirements and package); export gives the whole package as one JSON; pack gives the private links to the finished package for its owner.

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": {
      "pass_id": "<pass_id>",
      "part": "<part>"
    },
    "name": "co_invent_pass_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
partYes
pass_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / part / enum
      Previous value: -[
      -  "list",
      -  "overview",
      -  "brief",
      -  "opportunity",
      -  "shortlist",
      -  "concept",
      -  "brainstorm",
      -  "review",
      -  "mustdos",
      -  "requirements",
      -  "spec",
      -  "bom",
      -  "risks",
      -  "business",
      -  "market",
      -  "engineering",
      -  "diagrams",
      -  "patent",
      -  "claimcheck",
      -  "rounds",
      -  "app",
      -  "checks",
      -  "provenance",
      -  "activity",
      -  "export",
      -  "pack",
      -  "debbie",
      -  "attribution"
      -]New value: +[
      +  "list",
      +  "overview",
      +  "brief",
      +  "opportunity",
      +  "shortlist",
      +  "concept",
      +  "brainstorm",
      +  "review",
      +  "mustdos",
      +  "requirements",
      +  "spec",
      +  "bom",
      +  "risks",
      +  "business",
      +  "market",
      +  "engineering",
      +  "diagrams",
      +  "patent",
      +  "claimcheck",
      +  "rounds",
      +  "app",
      +  "checks",
      +  "provenance",
      +  "activity",
      +  "export",
      +  "pack",
      +  "debbie",
      +  "attribution",
      +  "reading",
      +  "commons"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / part / enum
      Previous value: -[
      -  "list",
      -  "overview",
      -  "brief",
      -  "opportunity",
      -  "shortlist",
      -  "concept",
      -  "brainstorm",
      -  "review",
      -  "mustdos",
      -  "requirements",
      -  "spec",
      -  "bom",
      -  "risks",
      -  "business",
      -  "market",
      -  "engineering",
      -  "diagrams",
      -  "patent",
      -  "claimcheck",
      -  "rounds",
      -  "app",
      -  "checks",
      -  "provenance",
      -  "activity",
      -  "export",
      -  "pack",
      -  "debbie"
      -]New value: +[
      +  "list",
      +  "overview",
      +  "brief",
      +  "opportunity",
      +  "shortlist",
      +  "concept",
      +  "brainstorm",
      +  "review",
      +  "mustdos",
      +  "requirements",
      +  "spec",
      +  "bom",
      +  "risks",
      +  "business",
      +  "market",
      +  "engineering",
      +  "diagrams",
      +  "patent",
      +  "claimcheck",
      +  "rounds",
      +  "app",
      +  "checks",
      +  "provenance",
      +  "activity",
      +  "export",
      +  "pack",
      +  "debbie",
      +  "attribution"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / part / enum
      Previous value: -[
      -  "list",
      -  "brief",
      -  "opportunity",
      -  "shortlist",
      -  "concept",
      -  "brainstorm",
      -  "review",
      -  "mustdos",
      -  "requirements",
      -  "spec",
      -  "bom",
      -  "risks",
      -  "business",
      -  "market",
      -  "engineering",
      -  "diagrams",
      -  "patent",
      -  "claimcheck",
      -  "rounds",
      -  "app",
      -  "checks",
      -  "provenance",
      -  "activity",
      -  "export",
      -  "pack",
      -  "debbie"
      -]New value: +[
      +  "list",
      +  "overview",
      +  "brief",
      +  "opportunity",
      +  "shortlist",
      +  "concept",
      +  "brainstorm",
      +  "review",
      +  "mustdos",
      +  "requirements",
      +  "spec",
      +  "bom",
      +  "risks",
      +  "business",
      +  "market",
      +  "engineering",
      +  "diagrams",
      +  "patent",
      +  "claimcheck",
      +  "rounds",
      +  "app",
      +  "checks",
      +  "provenance",
      +  "activity",
      +  "export",
      +  "pack",
      +  "debbie"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / part / enum
      Previous value: -[
      -  "list",
      -  "brief",
      -  "opportunity",
      -  "shortlist",
      -  "concept",
      -  "brainstorm",
      -  "review",
      -  "mustdos",
      -  "requirements",
      -  "spec",
      -  "bom",
      -  "risks",
      -  "business",
      -  "market",
      -  "engineering",
      -  "diagrams",
      -  "patent",
      -  "claimcheck",
      -  "rounds",
      -  "app",
      -  "checks",
      -  "provenance",
      -  "activity",
      -  "export",
      -  "pack"
      -]New value: +[
      +  "list",
      +  "brief",
      +  "opportunity",
      +  "shortlist",
      +  "concept",
      +  "brainstorm",
      +  "review",
      +  "mustdos",
      +  "requirements",
      +  "spec",
      +  "bom",
      +  "risks",
      +  "business",
      +  "market",
      +  "engineering",
      +  "diagrams",
      +  "patent",
      +  "claimcheck",
      +  "rounds",
      +  "app",
      +  "checks",
      +  "provenance",
      +  "activity",
      +  "export",
      +  "pack",
      +  "debbie"
      +]
  5. Changed1 schema field changed
    • changedInput schema / properties / part / enum
      Previous value: -[
      -  "list",
      -  "brief",
      -  "opportunity",
      -  "shortlist",
      -  "concept",
      -  "brainstorm",
      -  "review",
      -  "mustdos",
      -  "requirements",
      -  "spec",
      -  "bom",
      -  "risks",
      -  "business",
      -  "market",
      -  "engineering",
      -  "diagrams",
      -  "patent",
      -  "claimcheck",
      -  "rounds",
      -  "app",
      -  "checks",
      -  "provenance",
      -  "activity",
      -  "export"
      -]New value: +[
      +  "list",
      +  "brief",
      +  "opportunity",
      +  "shortlist",
      +  "concept",
      +  "brainstorm",
      +  "review",
      +  "mustdos",
      +  "requirements",
      +  "spec",
      +  "bom",
      +  "risks",
      +  "business",
      +  "market",
      +  "engineering",
      +  "diagrams",
      +  "patent",
      +  "claimcheck",
      +  "rounds",
      +  "app",
      +  "checks",
      +  "provenance",
      +  "activity",
      +  "export",
      +  "pack"
      +]
  6. Changed1 schema field changed
    • changedInput schema / properties / part / enum
      Previous value: -[
      -  "list",
      -  "brief",
      -  "opportunity",
      -  "shortlist",
      -  "concept",
      -  "brainstorm",
      -  "review",
      -  "mustdos",
      -  "requirements",
      -  "spec",
      -  "bom",
      -  "risks",
      -  "business",
      -  "market",
      -  "engineering",
      -  "diagrams",
      -  "patent",
      -  "claimcheck",
      -  "rounds",
      -  "app",
      -  "checks",
      -  "provenance",
      -  "activity"
      -]New value: +[
      +  "list",
      +  "brief",
      +  "opportunity",
      +  "shortlist",
      +  "concept",
      +  "brainstorm",
      +  "review",
      +  "mustdos",
      +  "requirements",
      +  "spec",
      +  "bom",
      +  "risks",
      +  "business",
      +  "market",
      +  "engineering",
      +  "diagrams",
      +  "patent",
      +  "claimcheck",
      +  "rounds",
      +  "app",
      +  "checks",
      +  "provenance",
      +  "activity",
      +  "export"
      +]
  7. Changed1 schema field changed
    • changedInput schema / properties / part / enum
      Previous value: -[
      -  "list",
      -  "brief",
      -  "shortlist",
      -  "concept",
      -  "brainstorm",
      -  "review",
      -  "mustdos",
      -  "requirements",
      -  "spec",
      -  "bom",
      -  "risks",
      -  "business",
      -  "market",
      -  "engineering",
      -  "diagrams",
      -  "patent",
      -  "claimcheck",
      -  "rounds",
      -  "app",
      -  "checks",
      -  "provenance",
      -  "activity"
      -]New value: +[
      +  "list",
      +  "brief",
      +  "opportunity",
      +  "shortlist",
      +  "concept",
      +  "brainstorm",
      +  "review",
      +  "mustdos",
      +  "requirements",
      +  "spec",
      +  "bom",
      +  "risks",
      +  "business",
      +  "market",
      +  "engineering",
      +  "diagrams",
      +  "patent",
      +  "claimcheck",
      +  "rounds",
      +  "app",
      +  "checks",
      +  "provenance",
      +  "activity"
      +]
  8. Changed1 schema field changed
    • changedInput schema / properties / part / enum
      Previous value: -[
      -  "list",
      -  "brief",
      -  "shortlist",
      -  "concept",
      -  "brainstorm",
      -  "review",
      -  "mustdos",
      -  "requirements",
      -  "spec",
      -  "bom",
      -  "risks",
      -  "business",
      -  "market",
      -  "engineering",
      -  "diagrams",
      -  "patent",
      -  "rounds",
      -  "app",
      -  "checks",
      -  "provenance",
      -  "activity"
      -]New value: +[
      +  "list",
      +  "brief",
      +  "shortlist",
      +  "concept",
      +  "brainstorm",
      +  "review",
      +  "mustdos",
      +  "requirements",
      +  "spec",
      +  "bom",
      +  "risks",
      +  "business",
      +  "market",
      +  "engineering",
      +  "diagrams",
      +  "patent",
      +  "claimcheck",
      +  "rounds",
      +  "app",
      +  "checks",
      +  "provenance",
      +  "activity"
      +]
  9. Added

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose an authentication requirement ('needs the signed-in link') and describes what several parts return (export gives one JSON, pack gives private package links). It never states the operation is read-only and side-effect free, nor does it explain the odd statement about a public link answering with 'how your person connects it,' which reads as unresolved setup chatter.

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 a single sprawling run-on: an ambiguous auth sentence, a legacy note, then an undifferentiated comma-spliced enumeration of ~28 part values. The actual purpose statement is buried third, and the one genuinely important detail (legacy alias) competes with trivia.

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 shapes need not be explained, and the description does cover auth and most part values. For a 30-value enum tool it is still incomplete: pass_id provenance is missing, several parts are unglossed, and the opening link sentence raises a question it never answers.

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 0%, so the description must compensate, and it does explain the meaning of several enum values (list, commons, reading, export, pack) plus the intent of the part list. But most of the roughly thirty enum values (overview, opportunity, checks, provenance, activity, debbie, attribution, rounds, app) get no gloss, and pass_id is never explained at all, not even where to obtain one.

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 third sentence, 'Read any part of a pass, as a person reads it in the app,' gives a specific verb and resource, and the description explicitly distinguishes itself from its sibling by calling itself an 'older name for co_invent_read.' The lead sentences about a signed-in link are confusing and obscure rather than sharpen the purpose, which keeps it out of 5 territory.

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?

Saying the tool is a legacy alias 'kept so a connector with a saved tool list keeps working' implicitly tells an agent to prefer co_invent_read for new work, which is useful routing. However, there is no explicit when-to-use/when-not statement, and nothing distinguishes reading a pass from co_invent_pass_status or co_invent_pass_step beyond the legacy note.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources