Skip to main content
Glama

hapana_status

Verifies that your Cotlet.dev account, credits, and Hapana connection are ready before using Hapana operations.

Instructions

Check that your Cotlet.dev account and Hapana are ready: account, credits and Hapana 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": "hapana_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 burden. 'Check' signals a non-mutating diagnostic and the description discloses the three things examined, but it says nothing about what the result looks like, whether it fails when not ready, or whether it consumes credits. Adequate but not rich for an unannotated tool.

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?

A single sentence with the verb and the full scope front-loaded, no filler and no redundant restatement of the tool name. Each listed item (account, credits, connection) adds information.

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 zero-parameter diagnostic with no annotations and no output schema, the description should indicate what a status check returns or how failure manifests. It names the checked areas but leaves the response shape entirely to inference, which is the main remaining gap.

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, so there is no parameter meaning to explain and the schema requires nothing further; the baseline of 4 applies. The description's mention of account/credits/connection describes what is inspected rather than inputs, so no parameter detail is missing.

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 concrete verb, 'Check', and enumerates the specific subjects it verifies: Cotlet.dev account, credits, and the Hapana connection. That distinguishes it from the sibling action tools (hapana_click, hapana_read, hapana_type) which perform operations rather than readiness diagnostics.

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?

'Check that ... are ready' implies a pre-flight/troubleshooting use before or after invoking the action siblings, but the description never states when to call this versus just attempting an operation, nor what to do on failure. Usage is only inferable, not stated.

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