Skip to main content
Glama
Sign In
@striderlabs/mcp-ubereats

@striderlabs/mcp-ubereats

by markswendsen-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ubereats_view_cart

View current cart contents including items, quantities, prices, and total cost with delivery fee.

Instructions

View the current cart contents, including all items, quantities, prices, and the total cost with delivery fee.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Description explicitly states it is a 'View' operation, implying no modifications. Given no annotations, it adequately conveys the non-destructive, read-only nature. Could be improved by noting behavior for an empty cart, but the current description is sufficient.

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?

Single sentence that is front-loaded with the core purpose ('View the current cart contents') and efficiently lists all key returned components. No filler or redundant information.

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?

Given zero parameters and no output schema, the description is complete. It explains what the tool returns and is sufficient for an agent to understand its function and expected output.

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 input schema has zero parameters and 100% coverage is trivial. The description adds value by enumerating the returned information (items, quantities, prices, total cost), which is not in the schema.

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?

Description clearly states the verb 'View' and the resource 'current cart contents', listing specific details like items, quantities, prices, and total cost. It distinguishes from sibling tools like ubereats_add_to_cart or ubereats_checkout by focusing on read-only retrieval.

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?

Usage context is implied (e.g., use to inspect cart before checkout), but no explicit guidance on when not to use it or comparison with alternatives like ubereats_status or ubereats_track_order. Lacks explicit when-to-use and when-to-avoid scenarios.

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

Deploy Server

Other Tools