Skip to main content
Glama

petpooja_open

Open a Petpooja page in your signed-in Cloud Browser to access sales reports and update menu items. Use the default billing URL or specify a page.

Instructions

Open a Petpooja page in your signed-in Cloud Browser (default https://billing.petpooja.com) to work with check sales reports and update menu items.

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_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://billing.petpooja.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully notes the browser is 'signed-in', implying session/auth is handled, but does not disclose whether navigation happens in a new tab or replaces the current page, what occurs if the page is already open, or how failures surface.

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?

A single front-loaded sentence with the action and default URL first, followed by intended uses. Nothing is redundant, though the trailing purpose clause is slightly loose.

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

Completeness3/5

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

For a one-optional-parameter navigation tool with no output schema, the description covers the what and the default target. It stops short of the behavior an agent needs at the start of a workflow: whether an existing page is reused, and what state the browser is left in for the follow-on click/read/type siblings.

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

Parameters3/5

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

There is a single optional parameter with 100% schema description coverage, and the schema already states the default URL. The description restates the same default without adding format constraints, allowed domains, or path/query expectations beyond what the schema provides.

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 uses a specific verb and resource ('Open a Petpooja page in your signed-in Cloud Browser') and adds the default destination URL plus the two concrete goals (check sales reports, update menu items). This distinguishes it from the interaction siblings (click, type, read, close), though it does not name any of them explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the task mention ('work with check sales reports and update menu items'), which signals this is the entry point before interacting. There is no explicit when-to-use guidance, no statement about whether to call petpooja_status first, and no note on what to do if a page is already open.

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