Skip to main content
Glama

petpooja_read

Reads the current Petpooja page to return visible text, numbered buttons, links, and fields, with optional element scoping for targeted page inspection.

Instructions

Read the current Petpooja page: its text and numbered buttons, links and fields.

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

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the behavioral burden. It usefully discloses the return content (page text plus numbered interactive elements), which is the key trait for a page-inspection tool, but says nothing about read-only safety, whether long pages are truncated, or how 'numbered' identifiers relate to sibling action tools.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One compact sentence with the resource and the returned contents front-loaded and zero filler. Every clause carries information useful to an agent deciding whether to call it.

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?

For a simple, non-destructive read tool with no output schema and no annotations, the description covers what the tool does and what it yields. It could go slightly further by explaining how the numbered elements are consumed by petpooja_click and whether reads are truncated, but nothing essential for correct invocation is missing.

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 ('Read only inside this element'), so the schema already explains it. The description adds no further meaning about the element scope or how indexing behaves when scoped, making the baseline 3 appropriate.

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 ('Read') and scoped resource ('the current Petpooja page'), and enumerates what comes back: text, numbered buttons, links and fields. This makes it distinguishable from siblings like petpooja_open (which presumably navigates) or petpooja_click (which acts on the numbered elements). It stops short of an explicit contrast with those siblings, so not a 5.

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?

There is no explicit guidance on when to call this versus alternatives; usage is only implied by the mention of 'numbered buttons', which hints you read the page to obtain indices before clicking or typing. No prerequisites, no mention of when a read is unnecessary (e.g., right after an action), and no exclusions.

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