Skip to main content
Glama

ezee_optimus_guide

Get guidance on using eZee Optimus screens for restaurant orders, kitchen tickets, and bills, including the sign-in link; call this before other actions.

Instructions

How to work in eZee Optimus (restaurant orders, kitchen tickets and bills): its screens and the sign-in link. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in eZee Optimus, in your words.

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 exist, so the description carries the full behavioral burden. It discloses the subject matter of the returned guidance (screens and sign-in link), implying an informational, non-mutating tool, but it never explicitly says this performs no actions or what form the answer takes. Modest but not misleading disclosure.

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?

Two short sentences with the directive 'Call this first' placed last for emphasis, and the topic scope front-loaded in parentheses. The phrase 'its screens and the sign-in link' is slightly loose, but there is no filler.

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-required-parameter orientation tool with no output schema and no annotations, the description covers what the guide is about and when to call it. What an agent still cannot tell is the shape of the response (prose guide vs. links) or whether calling it has any side effect, which matters given the total absence of annotations.

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

Parameters3/5

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

The single 'task' parameter is fully documented in the schema (100% coverage), so the baseline applies. The description adds nothing about how the free-text task phrasing shapes the guidance returned, so it neither helps nor hurts beyond the schema.

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 resource (workflow guidance for eZee Optimus — restaurant orders, kitchen tickets, bills) and enumerates what the guide covers (screens, sign-in link). It implicitly separates itself from the sibling action tools (click/open/close/type/read/status) by being the orientation resource, but never names a sibling, so differentiation is inferred rather than stated.

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

Usage Guidelines4/5

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

'Call this first' is an explicit, front-loaded sequencing instruction that tells the agent when to reach for this tool relative to everything else. It stops short of stating when-not to use it or pointing to a specific follow-up sibling, but the entry-point framing is clear.

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