Skip to main content
Glama

Recent orders

blinkit_orders

Retrieve the logged-in account's recent delivery orders with date, items, amount, and status; specify 1-10 orders, default 3.

Instructions

The logged-in account's recent Blinkit orders: when, what, how much, and status. Done by the engine's agent, so it needs a model on hunch-browser.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many orders (default 3)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/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, and it does disclose two useful facts: the data is scoped to the logged-in account and the call runs through the engine's agent requiring a model on hunch-browser. It omits what happens when no session exists (e.g., needing blinkit_login) and says nothing about ordering (most recent first?) or failure behavior.

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, no filler, with the resource and returned fields front-loaded. The trailing note about the engine's agent is slightly awkward but still earns its place by flagging a runtime prerequisite.

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 simple one-optional-parameter read tool with no output schema, the description gives a partial picture of the return values (when, what, how much, status) and a runtime prerequisite. It lacks the not-logged-in path and result ordering, which matter for an agent deciding how to call it.

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?

Schema coverage is 100% and the single optional `limit` parameter, including its default of 3 and max of 10, is fully documented in the schema. The description adds no additional meaning about how limit affects results, so the baseline 3 applies.

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?

States a specific resource and scope: 'The logged-in account's recent Blinkit orders', plus the fields returned (when, what, how much, status). An agent can tell this apart from sibling cart/checkout tools without opening the schema, though the operation verb (list/retrieve) is only implied.

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?

No statement of when to use this versus alternatives such as blinkit_view_cart or blinkit_status, and no exclusions. The 'recent orders' framing implies usage but nothing routes the agent explicitly.

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