Skip to main content
Glama

petpooja_status

Verifies your Cotlet.dev account, available credits, and Petpooja connection so you can confirm setup before querying reports or managing menu data.

Instructions

Check that your Cotlet.dev account and Petpooja are ready: account, credits and Petpooja connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 disclosure burden. It does well to enumerate the three things inspected and 'Check' implies a read-only, non-mutating operation, but it says nothing about failure behavior, whether it makes a live remote call, latency or rate limits, or what a negative result looks like. For a no-parameter status probe that gap is moderate rather than severe.

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 front-loaded sentence with no filler, and the core purpose appears first. The trailing colon list repeats 'account' from earlier in the sentence, which is a small redundancy rather than a real cost.

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?

With no parameters and no output schema, the definition needs mainly to say what is checked and why, which it does by enumerating account, credits, and connection. The main residual gap is that it does not characterize the response (per-component status versus a single boolean), which matters given there is no output schema to fall back on.

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

Parameters4/5

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

The tool takes zero parameters and the schema is an empty object with additionalProperties false, so there is no parameter meaning for the description to add. The baseline for a parameterless tool 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 gives a specific verb ('Check') and names the exact resources verified: Cotlet.dev account, credits, and Petpooja connection. That cleanly separates it from the sibling tools, which are browser interaction actions (open, click, type, read, close, guide). It stops short of a 5 only because it never states its relationship to those siblings in so many words.

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 framing ('ready') suggests a pre-flight or diagnostic check, but there is no explicit instruction such as 'call this before petpooja_open' or 'use this when authentication or credit errors occur.' No when-not-to-use condition is given either, so an agent must infer the diagnostic role from context.

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