Mews MCP Server and API by Cotlet

List arrivals in Mews

mews_list_arrivals

Read-onlyIdempotent

List arrivals in the user's own Mews account from ChatGPT, Claude or any AI agent. Returns how to do it in Mews step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Mews Cloud Browser. Mews's official API: Mews has a documented Connector API, but it has no official MCP server (checked 5 Nov 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": "mews_list_arrivals"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the bar is lower. The description adds genuine value beyond that: it discloses that the call performs no action on its own and only produces guidance, which is essential for correct sequencing. The API/MCP-server tangent adds background but little behavioral detail about the return payload.

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

Conciseness3/5

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

The purpose and the no-action/next-step constraint are front-loaded, which is good. However, the trailing sentence about Mews's Connector API and lack of an official MCP server does not help an agent decide or invoke, and the 'ChatGPT, Claude or any AI agent' phrase is filler, so not every sentence earns its place.

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?

For a zero-parameter, read-only tool with no output schema, the description covers what is returned (step-by-step Mews navigation guidance) and what must happen next (browser tools). That is sufficient for correct invocation, with the only gap being no hint about the shape or extent of the guidance returned.

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 has zero parameters, so the baseline is 4. There is nothing in the schema needing explanation, and the description correctly does not invent parameter semantics.

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 states a concrete resource (arrivals in the user's own Mews account) and, crucially, clarifies that the tool returns step-by-step instructions (screens, buttons, fields) rather than the data itself. This disambiguates the workflow from the cotlet_browser_* execution tools. The lead-in 'List arrivals' echoes the title and slightly overpromises what the call actually produces, but the second sentence corrects this.

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 gives explicit actionable guidance: this tool 'opens nothing by itself', so the agent must follow up with the cotlet_browser_* tools in the Mews Cloud Browser. That names the alternative and the sequencing. It does not specify which browser tools or how to chain them, and gives no explicit when-not-to-use, so it stops short of a 5.

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

All Mews MCP Server and API by Cotlet 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?