Skip to main content
Glama

AstraNL Coordination Protocol

find_offers

Read-onlyIdempotent

Find at most ten catalog offers for one demand, including measured networks and sellers found by rule through the global catalog. Unknown price basis and delivery remain UNKNOWN. No project, account, checkout, query cache or seller agreement. Read only. For a digest receipt of this read, confirmable through any door, call read_with_receipt.

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": {
      "demand": "<demand>"
    },
    "name": "find_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault
demandYesOne demand line; catalog matches are candidates.
postal_codeNo
delivery_countryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / receipt
      Removed value: -{
      -  "default": false,
      -  "type": "boolean"
      -}
  2. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description still adds real substance: a hard result cap of ten, an explicit disclosure that 'No project, account, checkout, query cache or seller agreement' is touched, and a warning that price basis and delivery stay UNKNOWN in the result — expectations an agent could not get from the annotations.

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?

Compact and front-loaded: the action and scope come first, constraints next, the receipt alternative last. Phrasing is telegraphic ('No project, account, checkout, query cache or seller agreement') but every clause carries information.

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 no output schema, the description does take on return-shape responsibility by stating the result is at most ten offers drawn from measured networks and rule-based sellers, with unknown price basis and delivery left unspecified. Combined with the safety annotations, that is nearly complete; only the meaning of the two optional location parameters is missing.

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?

Only 33% schema description coverage: 'demand' is documented in the schema, while postal_code and delivery_country carry patterns but no meaning. The description never explains the role of postal_code or delivery_country (e.g., that they narrow matches or are optional), and its mention of 'delivery remain UNKNOWN' refers to output uncertainty, not the parameter.

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?

States a concrete verb and resource ('Find catalog offers for one demand') plus a bounded scope ('at most ten') and what is included ('measured networks and sellers found by rule through the global catalog'). The one gap is that the object 'offers' is never defined in domain terms, and siblings like estimate_cost are not contrasted beyond read_with_receipt.

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 context is implied by 'for one demand' and the open-world catalog phrasing, and it explicitly routes the agent to read_with_receipt when a digest receipt is wanted. However, there is no statement of when NOT to use this versus estimate_cost or check_material, and no prerequisites are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources