Abstract
An invitation to act is something an organization lets an outside agent do: apply for a job, book a table, ask for a quote, buy a product, join a program. This proposal defines a shared list of these actions and one description of each, so an organization writes it once and publishes it as an MCP tool, an A2A skill and a schema.org action without three inconsistent definitions.
Status of this document
Version 0.1.0 is a problem statement and a proposed shape, open for public comment until 2027-01-31. The list of verbs and the fields are starting points for comment, not decisions.
1. The problem
The same action is described three ways in three places:
- schema.org uses
potentialActionwith types such asReserveActionorApplyActionand anEntryPointfor where to go. - MCP uses a tool with a free-form name, a description and a JSON Schema for its input.
- A2A uses a skill in an agent card, with an id, a description, tags and examples.
An organization that offers booking defines it three times, by hand, and the definitions drift. An agent comparing two businesses sees book_table, reserve and ReserveAction and must guess they are the same thing. Nothing tells it whether a person must confirm, what it will cost or what comes back.
2. Goals
- A small, shared list of verbs for the actions agents most often take with organizations.
- One description of an invitation that converts mechanically into each format.
- The facts an agent needs before acting: what it needs to provide, whether a person must confirm, the cost, and the result.
Not a goal: a new protocol. Invitations are published through the existing ones.
3. Proposed verbs
| Verb | Meaning | schema.org type |
|---|---|---|
apply |
Apply for a job, program, grant or account | ApplyAction |
book |
Reserve a time, table, room or seat | ReserveAction |
quote |
Ask for a price for a described need | (none; AskAction nearest) |
buy |
Purchase a product or service | BuyAction |
order |
Place an order fulfilled later | OrderAction |
join |
Become a member or subscriber | JoinAction, SubscribeAction |
register |
Sign up for an event | RegisterAction |
contact |
Reach a named person or team | CommunicateAction |
donate |
Give money | DonateAction |
check |
Ask for availability, status or eligibility | CheckAction |
4. Proposed description
invitation: book
name: Book a table
description: Reserve a table for up to 8 people, up to 30 days ahead.
inputs: # JSON Schema
type: object
required: [date, time, party_size]
properties:
date: {type: string, format: date}
time: {type: string, pattern: "^[0-2][0-9]:[0-5][0-9]quot;}
party_size: {type: integer, minimum: 1, maximum: 8}
confirmation: none # none | principal | organization
cost: free # free | fixed | quoted | variable
result: A booking reference and the time held.
endpoints:
mcp: {server: https://example.com/mcp, tool: book_table}
a2a: {card: https://example.com/.well-known/agent-card.json, skill: book-table}
web: https://example.com/book
policy: https://example.com/agents # see AR-3 Agent Policy
From this one description:
- the MCP tool takes
nameanddescription,inputsas its input schema, and an annotation forconfirmation; - the A2A skill takes the id, name, description and
invitationas a tag; - the schema.org action takes the mapped type, with
targetas anEntryPointat the web endpoint.
5. Open questions
- Is the verb list right? Which actions are missing, and which should merge?
- Should invitations live in a file of their own (for example
/.well-known/invitations.json) or only inside each protocol's own document? - How should cost be stated for variable prices without promising a figure?
- Should
confirmationfollow the human-in-the-loop terms of the protocols, where they exist, rather than define its own? - Which body should own the verb list once it settles: schema.org, the Agentic AI Foundation or another?
Changes
0.1.0 (2026-11-20)
First public draft: problem, goals, verbs and a proposed description. Opened for comment until 2027-01-31.