Meevo MCP Server and API by Cotlet

Pull daily sales in Meevo

meevo_pull_daily_sales

Read-onlyIdempotent

Pull daily sales in the user's own Meevo account from ChatGPT, Claude or any AI agent. Returns how to do it in Meevo step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Meevo Cloud Browser. Meevo's official API: Meevo has a Public API, but only after you send the request form with your Meevo Tenant ID and Millennium Systems reaches out with credentials (checked 11 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": "meevo_pull_daily_sales"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, which already establish read-only, non-destructive, idempotent behavior, the description discloses the critical non-obvious behavior: it opens nothing by itself and only returns step-by-step Meevo instructions. It also explains the API credential caveat, which materially affects how an agent should proceed.

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?

The purpose and handoff behavior are front-loaded and easy to extract. Some wording is less efficient, such as 'from ChatGPT, Claude or any AI agent' and the lengthy official-API aside, but the core structure remains clear.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, no-output-schema tool, the description is complete: it says what is returned (step-by-step screens, buttons, and fields), that it performs no action by itself, and which tools to use next. The annotations cover the safety profile, so no important context is 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 has zero parameters, so the baseline is 4. The description does not need to explain parameter semantics, and it correctly does not add irrelevant parameter details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: pulling daily sales in the user's own Meevo account. Crucially, it clarifies that the tool returns step-by-step instructions rather than performing the action, which distinguishes it from action-oriented siblings and prevents an agent from assuming it opens or reads Meevo directly.

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 says to use this for daily-sales guidance and then execute the steps with the cotlet_browser_* tools in the Meevo Cloud Browser. It also notes the official API route requires a request form and credentials, giving useful context on an alternative path, though it does not explicitly state when not to use this tool.

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

All Meevo 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?