Skip to main content
Glama
Sign In

Omio MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Find the cheapest day in Omio

omio_find_the_cheapest_day
Read-onlyIdempotent

Find the cheapest day in the user's own Omio account from ChatGPT, Claude or any AI agent. Returns how to do it in Omio step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Omio Cloud Browser. Omio's official API: Omio has no public API for your own account (checked 24 Oct 2026).

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": "omio_find_the_cheapest_day"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses the key behavioral facts: nothing is opened, no network action is taken, the output is procedural guidance, and execution requires the Omio Cloud Browser. The note that Omio has no public account API explains why the browser path is necessary, which is genuine context an agent cannot infer from annotations.

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 tight sentences that lead with what the tool does and follow with the required next step. The trailing API note ('checked 24 Oct 2026') is marginally extraneous and the date is oddly future-dated, but it is short and supports the rationale.

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?

With no input parameters, no output schema, and annotations covering safety, the description carries the remaining burden well by stating the return content (step-by-step screens, buttons, fields) and the required runtime (Omio Cloud Browser). Nothing essential for correct invocation appears missing.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing the description could add beyond what the empty schema already shows. Baseline for a parameterless tool applies.

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?

The description names a specific verb and resource ('Find the cheapest day ... Omio account') and immediately clarifies the actual output: step-by-step instructions (screens, buttons, fields) rather than the answer itself. This resolves the tension between the name 'find' and the real behavior, though an agent still has to reconcile that the tool does not literally return a cheapest day.

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

Usage Guidelines4/5

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

It clearly establishes the workflow condition: call this first to get instructions, then execute them with the cotlet_browser_* tools in the user's Omio Cloud Browser. It scopes usage to 'the user's own Omio account' versus a general search, but never explicitly contrasts with omio_search_trips or cotlet_app_guide.

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

All Omio MCP Server and API by Cotlet toolsInspect
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