Skip to main content
Glama

miocommerce_status

Verify your Cotlet.dev account, available credits, and MioCommerce connection before using the integration. Use it to confirm setup is ready and catch connection issues early.

Instructions

Check that your Cotlet.dev account and MioCommerce are ready: account, credits and MioCommerce 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": "miocommerce_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the three things inspected, which implies a non-mutating diagnostic, but never states read-only safety, whether external calls or latency are involved, or what happens if a check fails.

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?

A single front-loaded sentence with no padding. The colon list of checks is efficient, though the phrasing 'account, credits and MioCommerce connection' reads slightly awkwardly against the earlier 'Cotlet.dev account'.

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 the description is reasonably complete on what is inspected, but there is no output schema and no statement of what the response looks like (per-check status, error text) or what an agent should do on failure.

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 the baseline is 4. The description correctly implies the check is parameterless and covers all three dimensions at once, leaving nothing for an agent to supply.

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') plus the exact objects verified: account, credits, and MioCommerce connection. That is enough to separate it from the sibling action tools (click, close, open, read, type), though it never states the readiness verdict is returned rather than acted upon.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no prerequisite, and no contrast with siblings such as miocommerce_guide or the interaction tools. An agent must infer that this is a pre-flight diagnostic run before attempting MioCommerce operations.

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