Skip to main content
Glama

Saved addresses

blinkit_addresses

Retrieves the delivery addresses saved to a logged-in Blinkit account and identifies which address is currently selected.

Instructions

The delivery addresses saved on the logged-in Blinkit account, and which one is selected. 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_addresses"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

No annotations are supplied, so the description carries the full disclosure burden. It does add real context — the addresses belong to a logged-in account (a prerequisite) and the operation is performed by the engine's agent, requiring a model on hunch-browser — but it never states that this is a read-only operation, what happens if no session exists, or how the data comes back. Useful hints, incomplete disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is tight and front-loads the resource and its key extra detail (which address is selected). The second sentence is short but cryptic — 'done by the engine's agent, so it needs a model on hunch-browser' is internal runtime jargon that an agent cannot act on and that crowds out more useful guidance.

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-parameter read tool with no output schema, the definition covers what is returned at a high level and notes the logged-in prerequisite. It does not describe the shape of the response (a list of addresses plus a selection flag) or the failure mode when the account is not signed in, which for a session-dependent tool is a meaningful gap.

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 no parameter semantics to explain and the baseline is 4. Nothing in the description is needed to compensate for a schema gap.

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 concrete resource — the delivery addresses saved on the logged-in account — and adds that it returns which one is currently selected. That is specific enough to separate it from blinkit_orders, blinkit_view_cart and the other siblings. It is phrased as a noun phrase rather than a verb ('retrieve/list'), which is the only thing keeping it off a 5.

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 explicit when-to-use guidance: nothing says to call this before checkout, or how it relates to blinkit_set_location or blinkit_login. The reader can infer that it is a lookup of saved addresses, but the description never states a condition that selects this tool over an alternative.

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