MarketMan MCP Server and API by Cotlet

Get menu profitability in MarketMan

marketman_get_menu_profitability

Read-onlyIdempotent

Get menu profitability in the user's own MarketMan account from ChatGPT, Claude or any AI agent. Returns how to do it in MarketMan step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's MarketMan Cloud Browser. MarketMan's official API: MarketMan has a REST API (V3), but it needs an API Partner key and password, and its pricing page lists Open API Access as read-only in Enterprise or a paid add-on on Starter and Growth (checked 28 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": "marketman_get_menu_profitability"
  }
}

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?

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses the most important behavior: the tool performs no action and returns guidance, not results. The API licensing caveat (Partner key, read-only Open API in Enterprise / paid add-on) explains why browser automation is the path, adding real context the annotations 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.

Conciseness3/5

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

The first two sentences are front-loaded and high value, but the closing API paragraph is long and includes a questionable detail ("checked 28 Oct 2026") that reads as filler for an agent deciding how to call the tool. Useful rationale, but not tightly edited.

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 parameters and no output schema, the description does the needed work by stating the return content (step-by-step screens/buttons/fields) and the follow-up tool family. Nothing essential for correct invocation appears to be 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?

Zero parameters and 100% schema coverage, so there is nothing for the description to disambiguate. Baseline 4 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?

Names a specific verb+resource (get menu profitability) and, crucially, clarifies that it returns a step-by-step how-to (screens, buttons, fields) rather than the data itself, which prevents the agent from mistaking it for a data-fetch tool. It does not explicitly contrast with sibling marketman_get_actual_vs_theoretical_usage, so sibling differentiation is only partially handled.

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?

"opens nothing by itself; then do it with the cotlet_browser_* tools in the user's MarketMan Cloud Browser" gives a clear two-step workflow and names the alternative tools to use after. It stops short of stating exclusions (e.g., when to skip this and call the API or a list tool directly).

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

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