Skip to main content
Glama
Sign In
Sous

Sous

by Zawaer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Optional: Valio Aimo's offers (sponsored)

list_offers
Read-onlyIdempotent

Retrieve active Valio Aimo commercial offers for a buyer mandate, including signed prices, quantity caps, and validity dates, so you can present eligible deals to the buyer.

Instructions

Valio Aimo's active COMMERCIAL offers made to your buyer: signed (jws, typ sous-offer+jws) prices below the current one for a reason (near best-before, seasonal, a replacement for a recalled product, a new product), with a quantity cap and valid_until. Products the mandate rules out (avoided allergens, categories, claims) were never offered. Nothing is ordered: present each to the buyer as "Valio Aimo offers...", with its headline and disclosure, and only if the buyer wants it call request_quote with offer_id as how_to_accept says; the mandate decides as always (a first-time product may still need a human). Read-scoped like get_mandate: send your Authorization: Bearer header (or agent_token).

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": {
      "mandate_id": "<mandate_id>"
    },
    "name": "list_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault
mandate_idYes
agent_tokenNo

Output Schema

NameRequiredDescriptionDefault
noteNo
buyerYes
offersYes
disclosureYes
mandate_idYes
sponsored_byYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that nothing is ordered by this call, that results are pre-filtered by mandate rules (allergens, categories, claims), that offers carry a quantity cap and valid_until, and that the call is read-scoped with a required Bearer header or agent_token. That is substantial added context the annotations do not convey. It stops short of covering pagination or result volume, which keeps it off a 5.

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?

Front-loaded with what the offers are, then the buyer-facing workflow, then the auth note — a sensible order. It is dense and runs as a single long block, and the auth sentence is tacked on the end, but essentially every clause carries operational meaning and there is no filler.

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

Completeness4/5

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

With an output schema present, the description rightly omits return-value detail, and it covers the safety profile, mandate-based filtering, the downstream request_quote handoff, and authentication. The remaining gap is mechanical: nothing about result size, pagination, or the expected form of mandate_id for a 2-parameter read tool.

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 must carry the parameter burden. It does explain agent_token as an alternative auth path ('send your Authorization: Bearer header (or agent_token)'), but mandate_id's meaning is only implied through 'your buyer' and the mandate-filtering narrative rather than defined. It also names offer_id and how_to_accept, which are not parameters of this tool, so the parameter picture stays partial.

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?

States a specific verb and resource ('active COMMERCIAL offers made to your buyer') and then enumerates the offer contents: jws-signed prices below current, a stated reason (near best-before, seasonal, replacement, new product), a quantity cap, and valid_until. It also states a negative scope ('products the mandate rules out... were never offered'), which sharply bounds what the list contains and separates it from a general catalog search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use and how-to-follow-up guidance: present each offer to the buyer with its headline and disclosure, and only if the buyer wants it call request_quote with offer_id as how_to_accept says. It also flags the escalation condition ('a first-time product may still need a human') and states that the mandate decides as always.

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

Deploy Server

Other Tools