Skip to main content
Glama

Pumpkin

get_offerings

Read-only

Browse published general offerings and public prices.

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

Input Schema

NameRequiredDescriptionDefault
siteYesThe site ID returned by find_business.
limitNo
queryNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that only published/public items are returned, which is genuine scoping behavior beyond the annotations, but says nothing about pagination limits or result ordering for a browse-style list.

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 short sentence with no waste and the scope qualifier front-loaded. It is efficient, though the terseness borders on under-specification given four under-documented parameters.

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?

For a four-parameter paginated browse tool with no output schema and 25% schema coverage, the description is too thin. It should at least note that results are paged (limit/offset, max 30) and that `query` filters the listing, neither of which is discoverable from the description.

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 coverage is only 25% -- only `site` is documented in the schema, while limit, query, and offset are undocumented. The description does not mention any parameters at all, so it does not compensate for the coverage gap; an agent gets no hint that this endpoint supports search terms or paging.

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?

States a verb ("Browse") and a resource ("published general offerings and public prices"), so the general intent is legible. However, "general offerings" is vague and there is no differentiation from siblings like rental_search, service_search, or get_public_resources, which an agent could easily confuse with this tool.

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?

The description gives no when-to-use guidance and no exclusions relative to the many search/list siblings in the catalog. The only implicit signal is "published" and "public," which hints at scope but not at when to choose this over rental_search or service_search.

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