Skip to main content
Glama

AgentSynta Business Beacon

Search offerings

search_offerings
Read-onlyIdempotent

Search a business's published products and services with prices and (when shared) availability.

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": {
      "slug": "<slug>"
    },
    "name": "search_offerings"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesBusiness slug, e.g. 'harbor-bean'. Use list_businesses to find one.
typeNo
limitNo
queryNoText to match in name, description, category, SKU or attributes.
offsetNoUse next_offset from the previous page.
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Use next_offset from the previous page.",
      +  "maximum": 1000000,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • changedInput schema / properties / query / description
      Previous value: -"Text to match in name, description or category."New value: +"Text to match in name, description, category, SKU or attributes."
  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 readOnly, idempotent and openWorld, yet the description adds real behavioral context: only *published* offerings are returned (drafts excluded), prices are always included, and availability is conditional on the business having shared it. Fields being optionally absent is a useful disclosure the annotations cannot carry. Pagination and ordering behavior remain undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single well-formed sentence with no filler; the result payload is front-loaded right after the resource. Nothing to trim and nothing buried.

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

Completeness3/5

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

For a 6-parameter, read-only search with no output schema, the description omits how results are shaped beyond 'prices and availability' — no mention of paging via offset/next_offset, result ordering, or what a match on 'query' returns. Adequate for basic selection but thin given the undocumented parameters.

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 description coverage is only 50%, and three parameters (type, limit, category) have no schema description at all. The description mentions none of the six parameters, so it does not compensate for the gap — an agent gets no hint that 'type' filters product vs service or that 'limit' caps results.

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?

Specific verb ('Search') plus resource ('published products and services') and a stated payload ('prices and (when shared) availability'). The possessive 'a business's' implicitly scopes it to a single business, which contrasts with search_all_offerings, but the sibling is never named so the differentiation is inferred rather than stated.

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 is only implied: 'a business's' plus the required slug argument signal a per-business lookup, and the schema points to list_businesses for slug discovery. There is no explicit when-to-use/when-not statement and no mention of search_all_offerings as the cross-business alternative.

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