Salonized MCP Server and API by Cotlet

Get sales report in Salonized

salonized_get_sales_report

Read-onlyIdempotent

Get sales report in the user's own Salonized account from ChatGPT, Claude or any AI agent. Returns how to do it in Salonized step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Salonized Cloud Browser. Salonized's official API: Salonized has no public API, webhooks or MCP server (checked 31 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": "salonized_get_sales_report"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds traits annotations cannot express: the return value is procedural guidance rather than report data, and the tool performs no UI action itself. The note that Salonized has no public API/webhooks/MCP server explains why a browser-based path is required.

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?

Front-loaded and only three sentences, with the key disclosure about returning instructions placed early. Minor waste in 'from ChatGPT, Claude or any AI agent' and the awkward 'Salonized's official API:' fragment, plus an oddly specific freshness date that adds little.

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 no-parameter, no-output-schema guidance tool with strong annotations, the description covers what it returns, what it does not do, and how to act on the result. Nothing an agent needs in order to call it correctly 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 takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. Nothing in the description misleads about inputs.

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?

States a specific verb and resource (get sales report in the user's own Salonized account) and immediately corrects the likely misreading of the name by clarifying it 'Returns how to do it in Salonized step by step (screens, buttons, fields).' An agent can tell exactly what it gets back and that it is not a browser action.

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

Usage Guidelines5/5

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

Explicitly sequences usage: call this first to obtain instructions, 'then do it with the cotlet_browser_* tools in the user's Salonized Cloud Browser.' It also states the exclusion that it 'opens nothing by itself,' which cleanly separates this from the cotlet_browser_* siblings.

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

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