Petpooja MCP Server and API by Cotlet

Check online order payouts in Petpooja

petpooja_check_online_order_payouts

Read-onlyIdempotent

Check online order payouts 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_check_online_order_payouts"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The description goes beyond simple safety hints by stating crucial behavioral facts: it 'opens nothing by itself' and validates the lack of a public API, which manages user expectations about action vs. instruction.

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 definition is highly functional but slightly verbose. Every sentence is necessary to define the tool's scope and limitations, leading to strong functional clarity.

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?

Given that this tool serves as a guide to external browser tools and notes the absence of a public API, it is perfectly complete. It preemptively solves the user's biggest potential failure point: expecting an API call when only instructions are available.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Since the tool accepts no parameters (0), the description fulfills the baseline requirement for semantic clarity, as it is impossible to add meaningful parameter context.

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 purpose is stated immediately: checking online order payouts in the Petpooja account. It distinguishes its function as a guided instruction tool, not an execution tool, which is vital context.

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?

The description explicitly defines the usage context by stating it returns step-by-step instructions and clarifying that the user must then use the 'cotlet_browser_* tools.'

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?