Skip to main content
Glama

petpooja_click

Clicks a numbered element on the current Petpooja page to select controls, open menus, or trigger actions identified from the last page read.

Instructions

Click a numbered element on the current Petpooja page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "element": "<element>"
    },
    "name": "petpooja_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It never says what a click does (navigate, submit, trigger a destructive action), whether the element numbering becomes stale afterwards, whether results are awaited, or what happens if the element no longer exists. Only the 'current page' state dependency is conveyed.

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?

One short sentence with the action front-loaded and no filler. It is efficient, though its brevity is partly the reason behavioral details are missing rather than a sign of completeness.

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

Completeness2/5

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

This is a stateful, side-effecting browser interaction with no annotations and no output schema, so the description is the only source of behavioral detail and it supplies almost none. An agent cannot tell from it whether clicking is reversible, whether a follow-up read is required, or how failures manifest.

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?

Schema coverage is 100% and the single parameter is fully documented in the schema itself ('Element number from the last read'), so the description adds little beyond it. The mention of 'numbered element' is consistent with the schema but not additive; baseline 3 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?

The description names a specific verb ('Click') and a specific target ('a numbered element on the current Petpooja page'), which distinguishes it from siblings like petpooja_type, petpooja_read and petpooja_close. It stops short of explicitly contrasting itself with those siblings, but the action is unambiguous.

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 only implied: the phrase 'numbered element' plus the schema note 'Element number from the last read' hints that a petpooja_read must precede this call. There is no explicit statement of when to click versus type, or when the tool should not be used.

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