Skip to main content
Glama

petpooja_guide

Retrieve step-by-step guidance for Petpooja screens and sign-in before running any task. Use it to locate sales reports and menu update actions.

Instructions

How to work in Petpooja (check sales reports and update menu items): its screens and the sign-in link. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Petpooja, in your words.

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?

No annotations are supplied, so the description carries the full behavioral burden. It establishes that this is orientation/reference material ('its screens', 'the sign-in link') rather than an action, but it never explicitly says the call is read-only and performs no changes, leaving mild ambiguity against siblings named click/type/open.

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?

Two short clauses and a directive, with no wasted wording. The 'call this first' instruction is the key takeaway and could have been front-loaded for faster scanning, but nothing is padded.

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 small one-parameter guide tool with no output schema, the definition covers setup and sequencing. It does not tell the agent what a response looks like (link? screen list? step-by-step procedure?) or how it connects to the open/click/type siblings, which would matter for actually using the result.

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 parameter at 100% schema description coverage, so the schema already explains 'task' as free-text intent. The description only adds example task types (sales reports, menu updates), which is marginal added meaning beyond the schema.

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 states the tool is a usage guide for Petpooja, naming concrete covered areas ('check sales reports and update menu items') plus 'its screens and the sign-in link.' That is specific enough to distinguish it from the sibling UI-action tools (open/click/type/read), though it never says what form the guidance is returned in.

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?

'Call this first' gives explicit sequencing guidance relative to the sibling tools, which is the main routing decision an agent faces. It stops short of saying when not to use it or which sibling to pick for a specific follow-up action.

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