OiAir activities

list_offerings

Read-onlyIdempotent

List all current published groups belonging to one public organization at its current address. Each group retains its exact publication ID, version, schedule, prices and confirmation timestamps; an empty list does not authorize substituting another group.

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": {
      "organizationId": "<organizationId>"
    },
    "name": "list_offerings"
  }
}

Input Schema

Name	Required	Description	Default
`locale`	No
`organizationId`	Yes

Output Schema

Name	Required	Description	Default
`items`	Yes
`revision`	Yes
`syncedAt`	Yes
`generation`	Yes
`organizationId`	Yes
`bookingSemantics`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 1, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior, so the bar is lower. The description adds genuine value beyond that by enumerating what each returned group retains (publication ID, version, schedule, prices, confirmation timestamps) and by warning that an empty result does not authorize substitution.

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?

Two sentences, front-loaded with the core action and resource. The second sentence is dense and awkwardly worded ("does not authorize substituting another group"), but nothing is wasted.

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?

Safety behavior is covered by annotations and return content largely by the output schema, so the description doesn't need to carry those. However, with two undocumented parameters and a non-obvious locale filter, the definition leaves an agent without enough to call it precisely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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, yet it never names or explains the organizationId (required, UUID) or locale (enum) parameters. "One public organization at its current address" is an oblique nod to organizationId but adds no format or constraint detail.

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 ("List") and resource ("current published groups belonging to one public organization"), which clearly contrasts with the singular get_offering sibling. The terminology ("groups", "at its current address") is idiosyncratic and not tied to the tool name's vocabulary ("offerings"), leaving a slight gap, but the intent is legible.

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 (list offerings for a given organization) but no sibling is named and no explicit when-to-use/when-not guidance is given. The closing caveat about an empty list is a constraint, not selection guidance, so an agent must infer the choice against get_offering 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?