OiAir activities

get_offering

Read-onlyIdempotent

Read one exact, current published group by publication ID. Optionally require its expected version. Withdrawn, expired, changed-address or stale-version groups fail rather than falling back to another group. Published availability remains unknown.

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": {
      "publicationId": "<publicationId>"
    },
    "name": "get_offering"
  }
}

Input Schema

Name	Required	Description	Default
`locale`	No
`publicationId`	Yes
`expectedVersion`	No

Output Schema

Name	Required	Description	Default
`item`	Yes
`revision`	Yes
`syncedAt`	Yes
`generation`	Yes
`bookingSemantics`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 1, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description adds substantive behavior beyond that: withdrawn, expired, changed-address or stale-version records fail hard rather than falling back to a different record, and published availability may be unknown. It does not say what error or payload the caller gets on failure.

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

Conciseness4/5

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

Four short sentences, front-loaded with the core action and then the failure semantics. Every sentence carries information, though the trailing 'Published availability remains unknown' is ambiguous and costs clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 no explanation, and the failure/fallback behavior is well covered. The gaps are the undocumented locale parameter and the unclear meaning of 'published availability remains unknown' for a caller deciding whether to trust the result.

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 carry parameter meaning. It explains publicationId (the exact identifier) and expectedVersion (optional exact-version assertion) and that a mismatched version fails, but says nothing about the locale enum or how locale affects resolution.

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?

States a specific verb and scope: read ONE exact, current published item by publication ID, which implicitly separates it from list_offerings and search_activities. The term 'group' is used instead of 'offering', a slight terminology mismatch that could make an agent wonder whether it retrieves the same resource, so it stops short of a 5.

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?

Usage is implied (fetch a known publication by ID) rather than stated, and no sibling is named. It does add a real selection rule — pass expectedVersion to require an exact version — but there is no explicit when-to-use versus list_offerings or search_activities.

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

All OiAir activities 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.

Resources

Need Help?