Skip to main content
Glama

uber_eats_status

Verifies that your Cotlet.dev account, available credits, and Uber Eats connection are ready, helping you diagnose setup issues before managing stores, menus, or orders.

Instructions

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. 'Check' implies a read-only, non-mutating probe, but the description never confirms this, says whether it errors or returns a status when something is not ready, or how much of the state (account/credits/connection) is reported. For a zero-annotation tool this is a real gap.

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 front-loaded sentence with zero filler; the colon list quickly scopes the three things being verified. Nothing could be removed without losing 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?

The tool is simple and parameterless, and the description covers what it inspects, which is enough to invoke it. But with no annotations and no output schema, it should say what a result looks like (e.g., per-item ready/not-ready) or how failures surface, and it does not.

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 no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description's enumeration of what gets checked is a small bonus rather than a parameter concern.

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') and names the exact resources inspected: Cotlet.dev account, credits, and the Uber Eats connection. This clearly separates it from the sibling UI actions (uber_eats_click, uber_eats_open, uber_eats_type), though it never names them explicitly.

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?

The phrasing 'are ready' implies a pre-flight or sanity check before other operations, which is useful implied context. However, it gives no explicit when-to-use guidance, no prerequisites, and no statement about what to do if a check fails.

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