Skip to main content
Glama

ezee_optimus_status

Verify your Cotlet.dev account, available credits, and eZee Optimus connection before processing restaurant orders.

Instructions

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/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. 'Check' implies a non-mutating read, and the three checked resources (account, credits, connection) are useful behavioral disclosure, but nothing is said about what happens on failure, whether it is safe to call repeatedly, or what shape the result takes.

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 filler; the enumeration of the three checks is compact and scannable. The 'Cotlet.dev / eZee Optimus' branding is slightly noisy but not wasteful.

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?

This is a simple zero-parameter read, so the bar is low, but with no output schema the description should state what a result looks like (e.g., per-check pass/fail) and what the agent should do if a check fails. That gap leaves the agent unable to interpret the response confidently.

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 convey; baseline 4 applies. The description does not waste words describing nonexistent inputs.

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 a specific verb ('Check') and enumerates exactly what is inspected: account, credits, and the eZee Optimus connection. This clearly distinguishes it from the sibling action tools (click, close, open, read, type), though the description itself never names or contrasts with those alternatives.

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?

Readiness checking implies a pre-flight/verification use case, but the description never explicitly says when to call it (e.g., before starting a session, after credential changes) or when not to. The agent must infer the timing from the wording 'ready'.

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