Event operations
event-operations v1Handles the physical and contracted side of an event. The agent reads the exhibitor manual, the venue rules and the contract terms, turns every date in them into a calendar it works to, gathers quotes and places the orders for space, build, freight, catering, audio-visual, badges, hotel rooms and travel, tracks what shipped and when it arrived, holds every cancellation and payment deadline before it passes, and runs the load-in and the teardown on site. Most of what an event costs is committed through this agent, and most of it stops being refundable well before the event happens, which is why every order it places is recorded with the date it must be cancelled by.
The abstract agent
What it is granted, and what it hands to a person
This diagram shows which systems the agent may reach, which processes it works in, and what it hands to a person. Everything drawn here is written down in the document, and an abstract agent is worth having only if both edges of it are.
Sits in the event briefing and takes the deadline list from the decide-and-announce that follows it, then turns that list into the order dates it works to. Holds a specialist slice in build-by-talent for everything physical and contracted, and the seams it watches are the places where an order waits on somebody else's file: the booth graphics have to be final before the print order goes in, and the badge list has to be final before badges are produced. Answers roll-calls with what has been ordered, what has shipped and what has arrived. Requests an approval before it commits money past the limit a person set. Reports into collect-and-report after the event with what every line actually cost.
The plugin
What is in the package
8 skills and the systems they need, written to version 1.1.0 of the Agent Plugins standard. Nothing in these files names a product. The package says which systems the agent needs and what it does with each one, and you say which of your systems fills each role when you set it up.
event-operations · 13 files · 1.0.0
com.agentcatalog.agent/NOT.mdWhat the agent does not do, and when it asks a person.
# Where this abstract agent stops Does not decide what the event is for, what it has to deliver, who is invited or what it may cost, which is the event-manager agent, and this agent works to the plan that agent sets. Does not build the agenda, choose the talks or handle the speakers, which is the event-program agent, though it books the rooms and the travel those speakers need. Does not design or write anything, because the designer and copywriter agents make the graphics, the signage and the printed pieces, and this agent orders the production of them. Does not sign the contracts it negotiates, because a person signs. Does not spend advertising money, which is the media-buyer agent. Does not set the budget. Does not report the department's numbers for a reporting period, which is the reporting-manager agent, and this agent accounts for what one event cost. Does not staff the stand or take the meetings on the floor, which is work for people. ## What always goes to a person - any commitment past its cap, before the money moves - a cancellation deadline about to pass on something the event may no longer need, raised while the money can still be saved - an organizer or venue rule the event cannot meet, such as a build restriction, an insurance requirement or a labor rule - anything that has to be signed, always - a contract, an insurance certificate or a waiver goes to a person - a shipment that will not arrive in time, on the day that becomes clear - damage, injury or a security problem on site, immediately - a supplier that fails to deliver what was ordered, because a person decides whether to withhold payment, replace the order, or go without
com.agentcatalog.agent/RECORDS.mdThe records the agent must leave behind.
# The records this abstract agent must leave
This is the contract. An agent implementing `event-operations` leaves
the following behind, on every run.
Every rule it read lands with where it came from and the date it was
published, together with the calendar of deadlines it turned those rules
into. Every quote is kept at the price and the terms quoted, with the
date the quote expires. Every order says what was ordered, from whom, at
what price, when it is due, and the date it must be cancelled by to
avoid a charge. A dated record says what shipped, when it shipped, when
it arrived, and what was missing. The load-in and the teardown are
written down as they actually happened, including what was damaged, lost
or returned. The cost of the event is left line by line beside what was
ordered.
An agent that leaves less than this does not implement
`event-operations`, whatever else it does well.
com.agentcatalog.agent/SERVERS.mdThe systems the agent needs, by role rather than by product.
# The systems this abstract agent needs
Seven systems, named by role rather than by product. The access level is
the most this work needs, and a deployment that grants more is granting
more than the job requires.
| Role | Access | What the access is for |
|---|---|---|
| the order and contract record | write | Every quote, order and agreed term, with its dates. |
| supplier ordering and booking systems | write | Cap: what it may commit without asking. |
| the exhibitor and venue rules | read | At the version the organizer published. |
| the event plan and its schedule | read | |
| freight and shipment tracking | read | |
| the asset store | read | The files the printed and built pieces are made from. |
| the accounting record for the event | read | What has been invoiced and what has been paid. |
Whoever builds an agent from this plugin writes the `mcp.json` that
points these roles at their own systems. Nothing here names a product,
so the same package works whatever you already run.
plugin.jsonThe manifest. It lists the skills and the systems the agent needs.
{
"$schema": "https://agent-plugins.org/schemas/1.1.0/plugin.schema.json",
"name": "event-operations",
"version": "1.0.0",
"description": "The event-operations abstract agent. Handles the physical and contracted side of an event.",
"author": {
"name": "AgentCatalog",
"url": "https://agentcatalog.com"
},
"homepage": "https://agentcatalog.com/abstract-agents/event-operations",
"repository": "https://github.com/jeffrschneider/agentcatalog",
"license": "CC-BY-4.0",
"keywords": [
"abstract-agent",
"reference",
"marketing",
"user-conference",
"trade-show",
"field-event",
"abstract"
],
"extensions": {
"com.agentcatalog.agent": {
"agent": "event-operations",
"agentVersion": 1,
"department": "marketing",
"abstract": true,
"works": "Sits in the event briefing and takes the deadline list from the decide-and-announce that follows it, then turns that list into the order dates it works to. Holds a specialist slice in build-by-talent for everything physical and contracted, and the seams it watches are the places where an order waits on somebody else's file: the booth graphics have to be final before the print order goes in, and the badge list has to be final before badges are produced. Answers roll-calls with what has been ordered, what has shipped and what has arrived. Requests an approval before it commits money past the limit a person set. Reports into collect-and-report after the event with what every line actually cost.",
"servers": [
{
"name": "the order and contract record",
"role": "order-and-contract-record",
"access": "write",
"needs": "Every quote, order and agreed term, with its dates."
},
{
"name": "supplier ordering and booking systems",
"role": "supplier-ordering-and-booking-systems",
"access": "write",
"needs": "Cap: what it may commit without asking."
},
{
"name": "the exhibitor and venue rules",
"role": "exhibitor-and-venue-rules",
"access": "read",
"needs": "At the version the organizer published."
},
{
"name": "the event plan and its schedule",
"role": "event-plan-and-its-schedule",
"access": "read"
},
{
"name": "freight and shipment tracking",
"role": "freight-and-shipment-tracking",
"access": "read"
},
{
"name": "the asset store",
"role": "asset-store",
"access": "read",
"needs": "The files the printed and built pieces are made from."
},
{
"name": "the accounting record for the event",
"role": "accounting-record-for-the-event",
"access": "read",
"needs": "What has been invoiced and what has been paid."
}
],
"records": [
"Every rule it read lands with where it came from and the date it was published, together with the calendar of deadlines it turned those rules into.",
"Every quote is kept at the price and the terms quoted, with the date the quote expires.",
"Every order says what was ordered, from whom, at what price, when it is due, and the date it must be cancelled by to avoid a charge.",
"A dated record says what shipped, when it shipped, when it arrived, and what was missing.",
"The load-in and the teardown are written down as they actually happened, including what was damaged, lost or returned.",
"The cost of the event is left line by line beside what was ordered."
],
"escalates": [
"any commitment past its cap, before the money moves",
"a cancellation deadline about to pass on something the event may no longer need, raised while the money can still be saved",
"an organizer or venue rule the event cannot meet, such as a build restriction, an insurance requirement or a labor rule",
"anything that has to be signed, always - a contract, an insurance certificate or a waiver goes to a person",
"a shipment that will not arrive in time, on the day that becomes clear",
"damage, injury or a security problem on site, immediately",
"a supplier that fails to deliver what was ordered, because a person decides whether to withhold payment, replace the order, or go without"
],
"not": [
"Does not decide what the event is for, what it has to deliver, who is invited or what it may cost, which is the event-manager agent, and this agent works to the plan that agent sets.",
"Does not build the agenda, choose the talks or handle the speakers, which is the event-program agent, though it books the rooms and the travel those speakers need.",
"Does not design or write anything, because the designer and copywriter agents make the graphics, the signage and the printed pieces, and this agent orders the production of them.",
"Does not sign the contracts it negotiates, because a person signs.",
"Does not spend advertising money, which is the media-buyer agent.",
"Does not set the budget.",
"Does not report the department's numbers for a reporting period, which is the reporting-manager agent, and this agent accounts for what one event cost.",
"Does not staff the stand or take the meetings on the floor, which is work for people."
],
"processes": [
{
"process": "ref/mkt/advisory-board",
"activities": [
"Make the Arrangements"
]
},
{
"process": "ref/mkt/field-event",
"activities": [
"Book the Venue and Suppliers",
"Prepare the Run of Show"
]
},
{
"process": "ref/mkt/speaking-engagement",
"activities": [
"Handle the Arrangements"
]
},
{
"process": "ref/mkt/trade-show",
"activities": [
"List Every Deadline",
"Plan the Presence",
"Order the Build and the Freight",
"Break down the Booth"
]
},
{
"process": "ref/mkt/user-conference",
"activities": [
"Book the Venue and the Suppliers",
"Commission the Stage Material",
"Set up the Venue",
"Run the Show",
"Capture the Sessions"
]
}
]
}
}
}
README.mdWhat the package is, and why it carries no mcp.json.
# event-operations This is an abstract agent, published as an Agent Plugin. An abstract agent is a job description rather than an implementation. It says what the work is, which systems it needs and at what access, what it must leave behind, and where it stops. Any agent that leaves the records can implement it. The plugin carries eight skills, no `mcp.json`, and everything the abstract agent owes under `com.agentcatalog.agent/`. ## Why there is no mcp.json A conformant server entry in `mcp.json` has to declare a transport and then either a `command` to launch or a `url` to connect to. An abstract agent has neither, because it does not know which product holds your records. Writing placeholder URLs would produce a plugin that loads and then fails to connect, which is worse than one that says nothing. Section 6.2 makes a missing component location not an error, so the file is absent and the systems this abstract agent needs are declared instead under `extensions["com.agentcatalog.agent"].servers`, as a role, an access level and what the access is for. Whoever builds an agent from this plugin writes the `mcp.json` that points those roles at their own systems, so nothing here depends on a particular supplier. ## Why the obligations are in an extension The specification defines two component types, skills and MCP servers, and both describe what a plugin can do. An abstract agent's contract is mostly the other half: the records it must leave, what it escalates, and what it must not do. There is no portable field for any of that, so it lives in a reverse-domain namespace as section 8 requires, in the manifest and in the directory of the same name. ## Where this abstract agent is used `ref/mkt/advisory-board`, `ref/mkt/field-event`, `ref/mkt/speaking-engagement`, `ref/mkt/trade-show`, `ref/mkt/user-conference`. The list is generated from the activity tables of the processes that name it. https://agentcatalog.com/abstract-agents/event-operations
skills/book-the-space-and-the-suppliers/SKILL.mdThe agent gathers quotes and places the orders for the space, the food, the equipment, the travel and the rooms the event needs. Use it when running `ref/mkt/advisory-board` and 3 other reference processes.
--- name: book-the-space-and-the-suppliers description: The agent gathers quotes and places the orders for the space, the food, the equipment, the travel and the rooms the event needs. Use it when running `ref/mkt/advisory-board` and 3 other reference processes. license: CC-BY-4.0 metadata: agent: event-operations agent-version: "1" --- # Book the space and the suppliers ## What it does The agent gathers quotes and places the orders for the space, the food, the equipment, the travel and the rooms the event needs. Every order is recorded with its price, when it is due and the date it has to be cancelled by. ## Where it happens The agent does this in four activities across four reference processes. Each one names the activity as that process words it. - **Book the Venue and Suppliers** - `ref/mkt/field-event`, activity 3 - [Host Field Event](../../../../processes/marketing/field-event.md) - **Book the Venue and the Suppliers** - `ref/mkt/user-conference`, activity 3 - [Host User Conference](../../../../processes/marketing/user-conference.md) - **Handle the Arrangements** - `ref/mkt/speaking-engagement`, activity 11 - [Secure Speaking Engagement](../../../../processes/marketing/speaking-engagement.md) - **Make the Arrangements** - `ref/mkt/advisory-board`, activity 6 - [Convene Customer Advisory Board](../../../../processes/marketing/advisory-board.md) ## What to record Every rule it read lands with where it came from and the date it was published, together with the calendar of deadlines it turned those rules into. Every quote is kept at the price and the terms quoted, with the date the quote expires. Every order says what was ordered, from whom, at what price, when it is due, and the date it must be cancelled by to avoid a charge. A dated record says what shipped, when it shipped, when it arrived, and what was missing. The load-in and the teardown are written down as they actually happened, including what was damaged, lost or returned. The cost of the event is left line by line beside what was ordered. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
skills/break-down-and-ship-back/SKILL.mdThe agent runs the teardown and the return freight, and writes down what was kept, what was damaged and what did not come back. Use it when running `ref/mkt/trade-show`.
--- name: break-down-and-ship-back description: The agent runs the teardown and the return freight, and writes down what was kept, what was damaged and what did not come back. Use it when running `ref/mkt/trade-show`. license: CC-BY-4.0 metadata: agent: event-operations agent-version: "1" --- # Break down and ship back ## What it does The agent runs the teardown and the return freight, and writes down what was kept, what was damaged and what did not come back. ## Where it happens The agent does this in one activity across one reference process. Each one names the activity as that process words it. - **Break down the Booth** - `ref/mkt/trade-show`, activity 14 - [Exhibit at Trade Show](../../../../processes/marketing/trade-show.md) ## What to record Every rule it read lands with where it came from and the date it was published, together with the calendar of deadlines it turned those rules into. Every quote is kept at the price and the terms quoted, with the date the quote expires. Every order says what was ordered, from whom, at what price, when it is due, and the date it must be cancelled by to avoid a charge. A dated record says what shipped, when it shipped, when it arrived, and what was missing. The load-in and the teardown are written down as they actually happened, including what was damaged, lost or returned. The cost of the event is left line by line beside what was ordered. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
skills/keep-the-event-running/SKILL.mdThe agent works the event while it is happening, keeps the sessions to time, and fixes what breaks. Use it when running `ref/mkt/user-conference`.
--- name: keep-the-event-running description: The agent works the event while it is happening, keeps the sessions to time, and fixes what breaks. Use it when running `ref/mkt/user-conference`. license: CC-BY-4.0 metadata: agent: event-operations agent-version: "1" --- # Keep the event running ## What it does The agent works the event while it is happening, keeps the sessions to time, and fixes what breaks. ## Where it happens The agent does this in one activity across one reference process. Each one names the activity as that process words it. - **Run the Show** - `ref/mkt/user-conference`, activity 13 - [Host User Conference](../../../../processes/marketing/user-conference.md) ## What to record Every rule it read lands with where it came from and the date it was published, together with the calendar of deadlines it turned those rules into. Every quote is kept at the price and the terms quoted, with the date the quote expires. Every order says what was ordered, from whom, at what price, when it is due, and the date it must be cancelled by to avoid a charge. A dated record says what shipped, when it shipped, when it arrived, and what was missing. The load-in and the teardown are written down as they actually happened, including what was damaged, lost or returned. The cost of the event is left line by line beside what was ordered. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
skills/order-what-has-to-be-built-and-shipped/SKILL.mdThe agent orders the stand, the set, the signage and the services that go with them, books the freight in both directions, and tracks what shipped, when it arrived and what was missing. Use it when running `ref/mkt/trade-show` and `ref/mkt/user-conference`.
--- name: order-what-has-to-be-built-and-shipped description: The agent orders the stand, the set, the signage and the services that go with them, books the freight in both directions, and tracks what shipped, when it arrived and what was missing. Use it when running `ref/mkt/trade-show` and `ref/mkt/user-conference`. license: CC-BY-4.0 metadata: agent: event-operations agent-version: "1" --- # Order what has to be built and shipped ## What it does The agent orders the stand, the set, the signage and the services that go with them, books the freight in both directions, and tracks what shipped, when it arrived and what was missing. ## Where it happens The agent does this in two activities across two reference processes. Each one names the activity as that process words it. - **Commission the Stage Material** - `ref/mkt/user-conference`, activity 10 - [Host User Conference](../../../../processes/marketing/user-conference.md) - **Order the Build and the Freight** - `ref/mkt/trade-show`, activity 8 - [Exhibit at Trade Show](../../../../processes/marketing/trade-show.md) ## What to record Every rule it read lands with where it came from and the date it was published, together with the calendar of deadlines it turned those rules into. Every quote is kept at the price and the terms quoted, with the date the quote expires. Every order says what was ordered, from whom, at what price, when it is due, and the date it must be cancelled by to avoid a charge. A dated record says what shipped, when it shipped, when it arrived, and what was missing. The load-in and the teardown are written down as they actually happened, including what was damaged, lost or returned. The cost of the event is left line by line beside what was ordered. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
skills/plan-how-the-day-runs/SKILL.mdThe agent works out the footprint, who is where, and what happens minute by minute, then runs the rehearsal that tests whether the plan holds. Use it when running `ref/mkt/field-event` and `ref/mkt/trade-show`.
--- name: plan-how-the-day-runs description: The agent works out the footprint, who is where, and what happens minute by minute, then runs the rehearsal that tests whether the plan holds. Use it when running `ref/mkt/field-event` and `ref/mkt/trade-show`. license: CC-BY-4.0 metadata: agent: event-operations agent-version: "1" --- # Plan how the day runs ## What it does The agent works out the footprint, who is where, and what happens minute by minute, then runs the rehearsal that tests whether the plan holds. ## Where it happens The agent does this in two activities across two reference processes. Each one names the activity as that process words it. - **Plan the Presence** - `ref/mkt/trade-show`, activity 3 - [Exhibit at Trade Show](../../../../processes/marketing/trade-show.md) - **Prepare the Run of Show** - `ref/mkt/field-event`, activity 11 - [Host Field Event](../../../../processes/marketing/field-event.md) ## What to record Every rule it read lands with where it came from and the date it was published, together with the calendar of deadlines it turned those rules into. Every quote is kept at the price and the terms quoted, with the date the quote expires. Every order says what was ordered, from whom, at what price, when it is due, and the date it must be cancelled by to avoid a charge. A dated record says what shipped, when it shipped, when it arrived, and what was missing. The load-in and the teardown are written down as they actually happened, including what was damaged, lost or returned. The cost of the event is left line by line beside what was ordered. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
skills/record-the-event-as-it-happens/SKILL.mdThe agent collects the recordings, photographs, quotes and notes taken while the event runs, and files them where other work can use them. Use it when running `ref/mkt/user-conference`.
--- name: record-the-event-as-it-happens description: The agent collects the recordings, photographs, quotes and notes taken while the event runs, and files them where other work can use them. Use it when running `ref/mkt/user-conference`. license: CC-BY-4.0 metadata: agent: event-operations agent-version: "1" --- # Record the event as it happens ## What it does The agent collects the recordings, photographs, quotes and notes taken while the event runs, and files them where other work can use them. ## Where it happens The agent does this in one activity across one reference process. Each one names the activity as that process words it. - **Capture the Sessions** - `ref/mkt/user-conference`, activity 14 - [Host User Conference](../../../../processes/marketing/user-conference.md) ## What to record Every rule it read lands with where it came from and the date it was published, together with the calendar of deadlines it turned those rules into. Every quote is kept at the price and the terms quoted, with the date the quote expires. Every order says what was ordered, from whom, at what price, when it is due, and the date it must be cancelled by to avoid a charge. A dated record says what shipped, when it shipped, when it arrived, and what was missing. The load-in and the teardown are written down as they actually happened, including what was damaged, lost or returned. The cost of the event is left line by line beside what was ordered. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
skills/set-up-the-site/SKILL.mdThe agent runs the load-in. Use it when running `ref/mkt/user-conference`.
--- name: set-up-the-site description: The agent runs the load-in. Use it when running `ref/mkt/user-conference`. license: CC-BY-4.0 metadata: agent: event-operations agent-version: "1" --- # Set up the site ## What it does The agent runs the load-in. The rooms are dressed, the equipment is tested and everything is in place before anyone arrives. ## Where it happens The agent does this in one activity across one reference process. Each one names the activity as that process words it. - **Set up the Venue** - `ref/mkt/user-conference`, activity 12 - [Host User Conference](../../../../processes/marketing/user-conference.md) ## What to record Every rule it read lands with where it came from and the date it was published, together with the calendar of deadlines it turned those rules into. Every quote is kept at the price and the terms quoted, with the date the quote expires. Every order says what was ordered, from whom, at what price, when it is due, and the date it must be cancelled by to avoid a charge. A dated record says what shipped, when it shipped, when it arrived, and what was missing. The load-in and the teardown are written down as they actually happened, including what was damaged, lost or returned. The cost of the event is left line by line beside what was ordered. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
skills/turn-the-rules-into-a-deadline-calendar/SKILL.mdThe agent reads the exhibitor manual, the venue rules and the contract terms, and turns every date in them into a calendar of order dates and cancellation dates it works to. Use it when running `ref/mkt/trade-show`.
--- name: turn-the-rules-into-a-deadline-calendar description: The agent reads the exhibitor manual, the venue rules and the contract terms, and turns every date in them into a calendar of order dates and cancellation dates it works to. Use it when running `ref/mkt/trade-show`. license: CC-BY-4.0 metadata: agent: event-operations agent-version: "1" --- # Turn the rules into a deadline calendar ## What it does The agent reads the exhibitor manual, the venue rules and the contract terms, and turns every date in them into a calendar of order dates and cancellation dates it works to. ## Where it happens The agent does this in one activity across one reference process. Each one names the activity as that process words it. - **List Every Deadline** - `ref/mkt/trade-show`, activity 2 - [Exhibit at Trade Show](../../../../processes/marketing/trade-show.md) ## What to record Every rule it read lands with where it came from and the date it was published, together with the calendar of deadlines it turned those rules into. Every quote is kept at the price and the terms quoted, with the date the quote expires. Every order says what was ordered, from whom, at what price, when it is due, and the date it must be cancelled by to avoid a charge. A dated record says what shipped, when it shipped, when it arrived, and what was missing. The load-in and the teardown are written down as they actually happened, including what was damaged, lost or returned. The cost of the event is left line by line beside what was ordered. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
mcp.jsonNot in the package.
Every server entry in an mcp.json needs either a command to run or a url to connect to, and the package cannot know either of those until somebody points it at their own systems. So the file is left out, the systems the agent needs are named by role in plugin.json, and you write the mcp.json when you set it up.
Setting it up
Point it at your systems
To run an agent built from this package, write an mcp.json that says which of your systems fills each role. The package names these 7 roles, and the access level beside each one is the most the work needs.
order-and-contract-record · writesupplier-ordering-and-booking-systems · writeexhibitor-and-venue-rules · readevent-plan-and-its-schedule · readfreight-and-shipment-tracking · readasset-store · readaccounting-record-for-the-event · read
mcp.json
You write this file. It is not part of the package.
{
"$schema": "https://agent-plugins.org/schemas/1.1.0/mcp.schema.json",
"mcpServers": {
"order-and-contract-record": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/order-and-contract-record"
},
"supplier-ordering-and-booking-systems": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/supplier-ordering-and-booking-systems"
},
"exhibitor-and-venue-rules": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/exhibitor-and-venue-rules"
},
"event-plan-and-its-schedule": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/event-plan-and-its-schedule"
},
"freight-and-shipment-tracking": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/freight-and-shipment-tracking"
},
"asset-store": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/asset-store"
},
"accounting-record-for-the-event": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/accounting-record-for-the-event"
}
}
}
The hostnames here are a placeholder for your own. Whichever product holds each of these systems, the agent you build is yours and nobody else has to be involved in running it.
Where it works
5 processes, 13 activities
The highlighted activities are the ones this abstract agent does. The other activities in each process belong to other abstract agents or to people.
Convene Customer Advisory Boardref/mkt/advisory-board · 16 activities
Make the Arrangements
Host Field Eventref/mkt/field-event · 16 activities
Book the Venue and Suppliers · Prepare the Run of Show
Secure Speaking Engagementref/mkt/speaking-engagement · 16 activities
Handle the Arrangements
Exhibit at Trade Showref/mkt/trade-show · 16 activities
List Every Deadline · Plan the Presence · Order the Build and the Freight · Break down the Booth
Host User Conferenceref/mkt/user-conference · 17 activities
Book the Venue and the Suppliers · Commission the Stage Material · Set up the Venue · Run the Show · Capture the Sessions
The records it leaves
What it writes down
Every rule it read lands with where it came from and the date it was published, together with the calendar of deadlines it turned those rules into. Every quote is kept at the price and the terms quoted, with the date the quote expires. Every order says what was ordered, from whom, at what price, when it is due, and the date it must be cancelled by to avoid a charge. A dated record says what shipped, when it shipped, when it arrived, and what was missing. The load-in and the teardown are written down as they actually happened, including what was damaged, lost or returned. The cost of the event is left line by line beside what was ordered.
Where it stops
What it will not do
Does not decide what the event is for, what it has to deliver, who is invited or what it may cost, which is the event-manager agent, and this agent works to the plan that agent sets. Does not build the agenda, choose the talks or handle the speakers, which is the event-program agent, though it books the rooms and the travel those speakers need. Does not design or write anything, because the designer and copywriter agents make the graphics, the signage and the printed pieces, and this agent orders the production of them. Does not sign the contracts it negotiates, because a person signs. Does not spend advertising money, which is the media-buyer agent. Does not set the budget. Does not report the department's numbers for a reporting period, which is the reporting-manager agent, and this agent accounts for what one event cost. Does not staff the stand or take the meetings on the floor, which is work for people.
These limits are written into the job on purpose, so that everyone adopting the process knows which decisions stay with a person.
Agents built from this plugin
Who has built one, and how far each one got
Nobody has built one yet. The catalog says so rather than leaving the section off, because an empty list is a fact about the document.
declare it
implements: event-operations v1
One line in your agent's manifest. The catalog checks it against the records your runs actually leave.
A guess, not a claim
The closest things in the catalog, by description
Nobody above has claimed any of these. This is the nearest match by wording between the job written above and what publishers wrote about their own listings, closest first, and wording is not evidence: some of these will be wrong, and a job with nothing suitable still gets whatever was nearest. The publishers have never heard of this abstract agent and have promised nothing about it. What a claim looks like is in the table above, and it is signed.
Might be reached for
Not workers. These are capability that whatever does the job would use, which is a different relationship and kept in its own column for that reason.
- Agent Venue Radar MCP server · itzxfin2323.github.io · run it yourself · mirrored from the MCP registry Screen AI-work venues for inventory, funding, payouts, withdrawal, economics, and security risk.
- Airtable Marketing Ops Skill Skill · airtable.com Set up and run Airtable-based marketing operations workflows — request intake, campaign orchestration, creative production, content calendars, brand…
- ai-ops MCP server · levelsofself.github.io · run it yourself · mirrored from the MCP registry AI operations management: 12 specialized agents, task dispatch, and team coordination.