Skip to main content
Glama

Get offerings and prices

get_offerings
Read-onlyIdempotent

List what one entry of Daawid's registry offers, with prices and lead times, as its owner declared them: all of it, or what matches a few words, a category or an audience.

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": {
      "entry": "<entry>"
    },
    "name": "get_offerings"
  }
}

Input Schema

NameRequiredDescriptionDefault
entryYesWhich entry: its ID or slug, from search or get_entry.
limitNo
queryNoOnly offerings with these words: "kitchen".
cursorNonextCursor of the previous page.
audienceNoOnly offerings for this audience, and those for everyone.
categoryNoOnly this category ("trades.carpentry") or sector ("trades").
languageNoThe language the user writes in: "en". The answer comes in it, when the entry has it.

Output Schema

NameRequiredDescriptionDefault
urlYes
slugYes
mediaNo
totalYes
entryIdYes
languageYes
revisionYes
offeringsYes
nextCursorNo
displayNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds one real piece of context beyond that — the data is 'as its owner declared them', signalling owner-supplied, unverified content. It does not mention pagination or result limits, which the cursor/limit params imply.

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?

A single sentence, front-loaded with the core action and resource, with no filler. The trailing 'all of it, or what matches...' clause is slightly compressed but still parses cleanly.

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 and 86% schema coverage, the description needn't explain return values or field semantics. It conveys the entity scope, filter modes, and the owner-declared nature of the data; only pagination behaviour is left implicit.

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 86%, so the schema already documents entry, query, category and audience. The description's mention of 'a few words, a category or an audience' mirrors those params without adding syntax, defaults, or interaction rules (e.g. how query and category combine). Baseline 3 is appropriate.

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?

The description names a specific verb and resource ('List what one entry of Daawid's registry offers') and states what the payload contains ('prices and lead times'). It is clear enough to distinguish from search or get_entry, but it never names or contrasts a sibling explicitly.

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?

The phrase 'all of it, or what matches a few words, a category or an audience' communicates the two usage modes (full listing vs filtered listing) implicitly. There is no explicit when-to-use versus alternatives such as search or get_entry, and no stated exclusions.

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