Fetch a single Eventarc event by its list-derived ID to inspect attributes, payload data, and every function delivery's outcome, duration, and invocation ID.
One Eventarc event with its attributes, data and every function delivery (outcome, duration, invocation id for functions_get_call).
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The event id from eventarc_list_events (<nonce>-<seq>), not the CloudEvent id |
Changes observed during successful MCP inspections.
v0.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Since no annotations are provided, the description performs the crucial task of disclosing behavioral traits by listing specific returned metadata, such as outcome, duration, and invocation id for function delivery.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The definition is concise, delivering maximum functional information in a single, dense sentence without unnecessary jargon.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
By detailing exactly what data is returned (attributes, data, delivery info), it provides sufficient context for an agent even without a formalized output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Although schema coverage is 100%, the description adds essential domain knowledge regarding the specific ID format and its source, preventing the agent from passing a CloudEvent ID incorrectly.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves a specific Eventarc event, including its attributes and associated function delivery data. It identifies the target resource and what it contains.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly guides usage by clarifying that the ID must come from eventarc_list_events and uses the specific format (<nonce>-<seq>), which distinguishes it from a CloudEvent ID.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.