io.github.AndrewVG23/grocery-mcp

get_grocery_handoff

Fetch a previously created grocery product-link handoff using its unique ID to access saved product links.

Instructions

Retrieve a previously generated product-link handoff.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "handoff_id": "<handoff_id>"
    },
    "name": "get_grocery_handoff"
  }
}

Input Schema

Name	Required	Description	Default
`handoff_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 4, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries full responsibility. It adds no behavioral context beyond what the name suggests—it does not state idempotency, error behavior (e.g., 404 if not found), or that it is a safe read-only operation. The phrase 'previously generated' implies persistence but provides no safety or side-effect information.

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?

The description is a single concise sentence with no fluff. It is front-loaded with the action and resource, making it easy to scan.

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

Completeness2/5

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

While the tool is simple and an output schema exists, the description omits usage context relative to sibling tools (e.g., relationship to 'create_handoff_from_template'). It does not mention edge cases or when to use this instead of listing templates. The description is minimally complete for a basic get, but lacks enough context for an agent to make fully informed decisions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has no description for 'handoff_id', and the description does not compensate. It only implies that the ID refers to a previously generated handoff but does not explain its format, source (e.g., from a create response), or any constraints. With 0% schema coverage, the description should provide more parameter context.

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?

The description uses a specific verb 'retrieve' and a specific resource 'product-link handoff', clearly distinguishing this get operation from sibling tools that create or list handoffs/templates. The purpose is immediately clear.

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 is implied: you use this tool when you want to fetch a previously generated handoff. However, there is no explicit guidance on when to prefer this over listing templates or creating from template, nor any alternative names mentioned.

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

Deploy Server