Petpooja MCP Server and API by Cotlet

Get sales report in Petpooja

petpooja_get_sales_report

Read-onlyIdempotent

Get sales report in the user's own Petpooja account from ChatGPT, Claude or any AI agent. Returns how to do it in Petpooja step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Petpooja Cloud Browser. Petpooja's official API: Petpooja publishes no API documentation or API keys page for restaurants (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": "petpooja_get_sales_report"
  }
}

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 annotations, the description adds meaningful behavior: the tool 'opens nothing by itself' and only returns procedural text, so no account state changes. It also explains why browser automation is required by noting Petpooja publishes no API documentation or keys for restaurants, which justifies the manual path.

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 key facts are front-loaded, but the content is packed into one long run-on sentence, and the opening phrase 'from ChatGPT, Claude or any AI agent' is filler that doesn't help an agent decide. The API-availability note earns its place but would read better as a separate sentence.

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, no output schema, and annotations covering safety, the description supplies the pieces an agent needs: what is returned (step-by-step screens/buttons/fields), what is not done (no browser action), and the follow-up tool family. A short note on whether the steps are tailored to the user's outlet/role would close the remaining gap.

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?

There are zero parameters, so the baseline is 4. The description correctly implies no inputs are needed (the tool just returns guidance); nothing about parameter meaning is left ambiguous.

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 makes the actual behavior explicit: it returns step-by-step Petpooja navigation instructions (screens, buttons, fields) rather than fetching report data, which is critical because the name 'get_sales_report' implies data retrieval. It also names the cotlet_browser_* tools as the follow-up, distinguishing this guidance tool from the browser-action siblings.

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 states the workflow clearly: this tool yields the how-to, then the agent must execute it with cotlet_browser_* tools in the Petpooja Cloud Browser. What's missing is any exclusion, e.g. when not to use this guide versus the direct Petpooja data tools in the catalog.

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

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