Skip to main content
Glama
Sign In

A2A Retailmedia — the agentic retail-media hub for grocery

by io.github.greencore-solutions
OverviewDiscussionsAdmin

Quote Package

quote_package
Read-onlyIdempotent

Price it: returns where the banner's own media program publishes its rates or takes an enquiry. wefetch never prices; a quote comes from the retailer's program.

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": {
      "market": "<market>",
      "banner": "<banner>"
    },
    "name": "quote_package"
  }
}

Input Schema

NameRequiredDescriptionDefault
bannerYes
marketYes
decision_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedOutput schema / additionalProperties
      Removed value: -true
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare this a safe, idempotent read. The description adds genuinely useful behavior: it does not compute prices and instead returns pointers to the retailer's program. It does not describe how many sources come back or what happens when no program is found, so the added context is partial.

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?

Two short sentences with no padding, and the key constraint is present. However, the leading 'Price it:' works against the actual behavior and forces the reader to reconcile contradictory framing.

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?

An output schema exists, so return values need not be explained. What is missing is scope semantics for market and banner and a mention of decision_id, which are needed to call a rate-directory lookup correctly; the description otherwise covers the tool's stance on pricing.

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?

Schema description coverage is 0% for three parameters. The description mentions only 'the banner' indirectly and says nothing about 'market' (presumably country/currency scope) or 'decision_id'. For a lookup whose result depends heavily on market and banner, this leaves the agent guessing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says the tool returns where the banner's own media program publishes rates or takes an enquiry, which is a lookup of a pricing/enquiry destination rather than a price. But it opens with 'Price it', which conflicts with 'wefetch never prices' and muddies the verb. An agent can infer the resource but not cleanly the action.

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?

It implicitly tells the agent to use this when a quote or rate is needed, and explicitly rules out wefetch-side pricing. There is no comparison to alternatives among siblings (e.g. list_packages, check_eligibility) and no stated prerequisites.

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

All A2A Retailmedia — the agentic retail-media hub for grocery toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources