A2A Retailmedia — the agentic retail-media hub for grocery

Submit Demand

submit_demand

Hand off: the packet — the maker, a budget a person has approved, one or more GTINs, a market and a list of banners — or a gap naming what is missing. Routes each banner by its card status: unclaimed is a referral, claimed goes to the retailer's media team, registered goes agent to agent. Settles at the door.

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": {
      "maker": "<maker>",
      "budget": "<budget>",
      "budget_approved_by": "<budget_approved_by>",
      "gtins": "<gtins>",
      "market": "<market>",
      "banners": "<banners>",
      "contact": "<contact>"
    },
    "name": "submit_demand"
  }
}

Input Schema

Name	Required	Description	Default
`note`	No
`gtins`	Yes
`maker`	Yes
`budget`	Yes
`market`	Yes
`banners`	Yes
`contact`	Yes
`decision_id`	No
`budget_approved_by`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 11, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedOutput schema / additionalProperties
```
Removed value: -true
```
First observedOct 5, 2026

TDQS

C2.7/5.0

Behavior3/5

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

The routing rule (unclaimed=referral, claimed=retailer media team, registered=agent-to-agent) is real behavioral context beyond the annotations, which only declare it is a non-readOnly, openWorld write. However, the description leaves permission/auth requirements opaque and 'Settles at the door' conveys nothing actionable.

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?

Three dense sentences that are front-loaded starting with the intent, but the flowery wording ('the packet', 'Settles at the door') consumes space without adding callable meaning.

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?

An output schema exists so return values need not be explained, but for a 7-required-parameter write tool the description omits key parameters and any auth/precondition context, and its colorful closing image is opaque rather than informative.

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 description coverage is 0%, so the description carries the full param burden. It maps well to six of the nine (maker, budget, budget_approved_by via 'a budget a person has approved', gtins, market, banners) but never mentions contact, note, or decision_id, leaving required 'contact' undocumented anywhere.

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 names a concrete payload (maker, approved budget, GTINs, market, banners) and the routing behavior, so the agent can infer this submits a demand. However, the framing verb 'Hand off' and phrases like 'Settles at the door' are cryptic and it never distinguishes itself from close siblings such as a2a_handoff or receive_demand.

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 or when-not-to-use guidance and no named alternative, despite several plausible routing siblings. The clause 'or a gap naming what is missing' hints at a failure mode but not at when the agent should reach for this tool over the others.

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 tools Inspect

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.