OiAir activities

search_activities

Read-onlyIdempotent

Search OiAir public activities using its current search API, ranking and filters. Age is inclusive; weekdays use Sunday=0 through Saturday=6, and any selected day may match. Age, day and time must match the same published group. Keep unresolved constraints and unknown availability; results do not confirm a place.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_activities"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	No
`cursor`	No
`locale`	No
`filters`	No

Output Schema

Name	Required	Description	Default
`items`	Yes
`nextCursor`	Yes
`queryStatus`	Yes
`appliedFilters`	Yes
`bookingSemantics`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 1, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuine behavioral context beyond that: 'Keep unresolved constraints and unknown availability; results do not confirm a place' warns the agent not to over-trust results, which is exactly the kind of insight structured fields cannot carry.

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?

Compact and front-loaded, with the core verb-resource stated first and constraints following. Sentences are dense and slightly cryptic in places, but nothing is wasted.

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 annotations cover the safety profile. The one gap is that cursor/limit pagination behavior is never mentioned despite the cursor param existing.

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 compensate. It does explain age inclusivity and the Sunday=0..Saturday=6 mapping for days, plus the cross-field grouping rule, but it is silent on query, limit, cursor, locale, price, bounds, period and categories.

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 resource: 'Search OiAir public activities'. An agent knows what the tool does, but it never distinguishes itself from the sibling list_offerings, which could plausibly be used for a similar browsing goal.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not guidance, and no sibling is named. The semantic notes (age/day matching) describe result interpretation rather than helping the agent choose this tool over the alternatives.

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?