Skip to main content
Glama

View cart

blinkit_view_cart

View every item, quantity, and bill line in the Blinkit cart, including items total, delivery, handling, surge or small-cart fees, and the grand total before checkout.

Instructions

The Blinkit cart: items, quantities, and the bill row by row (items total, delivery, handling, any surge or small-cart fee) with the grand total.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the returned payload in useful detail, including fee rows (delivery, handling, surge, small-cart fee) and the grand total, which is genuinely valuable given there is no output schema. However, it never states that the call is read-only, what happens if the cart is empty, or whether authentication/location state is required, leaving real behavioral gaps for a zero-parameter tool.

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?

It is a single front-loaded sentence with no filler, and the parenthetical efficiently enumerates the bill components that would otherwise need a schema. The only weakness is that it is phrased as a noun fragment rather than an action statement, and listing every fee type is slightly more detail than an agent needs to select the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple, zero-parameter read tool with no output schema, the description covers the return shape well enough that an agent knows what it will get back. The remaining gaps — empty-cart behavior and login/location prerequisites — are minor but would matter for correct sequencing with blinkit_login or blinkit_set_location.

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 nothing for the description to disambiguate; the baseline of 4 applies. Nothing in the text misleads about 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 names the resource (the Blinkit cart) and enumerates its contents — items, quantities, and a row-by-row bill with grand total — so an agent can tell it retrieves cart state rather than mutating it. It stops short of an explicit verb like 'view' or 'retrieve' and never contrasts itself with blinkit_update_cart or blinkit_add_to_cart, so differentiation is inferred from the noun phrase alone.

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 when-to-use guidance, no statement of prerequisites such as being logged in or having a selected location, and no mention of alternatives like blinkit_live_view or blinkit_update_cart. The agent must infer that this is the read path for cart contents purely from the name and payload listing.

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