Skip to main content
Glama

Check the setup

wopee_setup_check
Read-onlyIdempotent

Verifies Wopee.io connection and returns project name, UUID, plan, steps left and reset time. Diagnoses rejected keys, missing UUIDs or project mismatches. Read-only; run after setup.

Instructions

Verify that Wopee.io is connected: returns the project name and UUID, app URL, plan, steps left, reset time and the Commander link for the project of WOPEE_API_KEY, and names the problem when the key belongs to another project than WOPEE_PROJECT_UUID, the UUID is missing or the key is rejected. Read-only, takes no input. Call it as the last step of a setup and whenever a tool answers Not Authorised!.

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": "wopee_setup_check"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.37.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover readOnlyHint, idempotentHint and destructiveHint, but the description still adds real behavior: no input is consumed, the exact payload fields are enumerated, and the three specific failure modes (key belongs to another project, missing UUID, rejected key) are named as reported errors rather than thrown exceptions. Nothing contradicts the annotations; the only gap is that it does not say what a failed check looks like in the response shape.

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?

The purpose is front-loaded in the first clause and every subsequent phrase adds information (returned fields, error conditions, usage triggers). It is one dense sentence rather than a structured list, which makes it slightly harder to scan, but no wording is redundant.

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

Completeness5/5

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

With no output schema, the description carries the burden of describing return values and does so field by field, plus it explains the error-reporting contract. For a zero-parameter, read-only verification tool this leaves nothing an agent needs unanswered.

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?

Zero parameters, so the baseline is 4, and the description reinforces it with "takes no input", removing any doubt about whether arguments are required. There is nothing further to document, so it cannot exceed the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Verify that Wopee.io is connected" names a specific verb and resource, and the sentence then enumerates exactly what the call returns (project name, UUID, app URL, plan, steps left, reset time, Commander link), so the agent knows precisely what this tool produces. It is clearly a diagnostic/status tool, distinct from the sibling fetch/create/update tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Two explicit triggers are given: "Call it as the last step of a setup" and "whenever a tool answers Not Authorised!". That second clause is unusually actionable recovery guidance, since it tells the agent what to do after a failure of another tool rather than leaving the fallback to inference.

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