Skip to main content
Glama

AgentSynta Business Beacon

Search all offerings

search_all_offerings
Read-onlyIdempotent

Search eligible published offers across AgentSynta without a slug using literal keywords or conservative buyer criteria; returns applied criteria and stored match evidence, never FX or distance estimates.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_all_offerings"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoAlias of query; conflicting aliases are rejected.
typeNo
limitNo
queryNoLiteral search text; budget and bedroom phrases are understood, e.g. 'three bedroom home under £500,000'. Put the place in location (e.g. London), not in the query. Unsupported residual words remain literal constraints.
cursorNoUse next_cursor from the previous page (works at any depth).
offsetNoUse next_offset from the previous page.
bedroomsNoExact affirmative bedroom count from description or Bedrooms attribute, never inferred from Rooms=3+2.
categoryNoExact category (case-insensitive).
currencyNoThree-letter currency code; £ implies GBP, € implies EUR; bare $ requires explicit currency.
locationNoTextual offering locality or business city/region/country, e.g. London, Sydney or New York; never a distance claim. Only the alias groups Nicosia/Lefkoşa/Lefkosa/Nicossia and North Cyprus/NC are normalised.
max_priceNoInclusive maximum price; currency required. Conflicting inferred budgets are rejected.
min_priceNoInclusive minimum price; currency required. No FX conversion.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / location / description
      Previous value: -"Textual offering locality or business city/region/country; Nicosia/Lefkoşa/Lefkosa/Nicossia and North Cyprus/NC normalize, never a distance claim."New value: +"Textual offering locality or business city/region/country, e.g. London, Sydney or New York; never a distance claim. Only the alias groups Nicosia/Lefkoşa/Lefkosa/Nicossia and North Cyprus/NC are normalised."
    • changedInput schema / properties / query / description
      Previous value: -"Literal search or supported phrases: three bedroom home near Nicosia under £500,000; property with 3 bedrooms in North Cyprus. Unsupported residual words remain literal constraints."New value: +"Literal search text; budget and bedroom phrases are understood, e.g. 'three bedroom home under £500,000'. Put the place in location (e.g. London), not in the query. Unsupported residual words remain literal constraints."
  2. Changed8 schema fields changed
    • addedInput schema / properties / bedrooms
      Added value: +{
      +  "description": "Exact affirmative bedroom count from description or Bedrooms attribute, never inferred from Rooms=3+2.",
      +  "maximum": 20,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / currency
      Added value: +{
      +  "description": "Three-letter currency code; £ implies GBP, € implies EUR; bare $ requires explicit currency.",
      +  "pattern": "^[A-Za-z]{3}$",
      +  "type": "string"
      +}
    • changedInput schema / properties / location / description
      Previous value: -"Business city, region or country."New value: +"Textual offering locality or business city/region/country; Nicosia/Lefkoşa/Lefkosa/Nicossia and North Cyprus/NC normalize, never a distance claim."
    • addedInput schema / properties / max_price
      Added value: +{
      +  "description": "Inclusive maximum price; currency required. Conflicting inferred budgets are rejected.",
      +  "maximum": 1000000000000,
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / min_price
      Added value: +{
      +  "description": "Inclusive minimum price; currency required. No FX conversion.",
      +  "maximum": 1000000000000,
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / q
      Added value: +{
      +  "description": "Alias of query; conflicting aliases are rejected.",
      +  "maxLength": 300,
      +  "type": "string"
      +}
    • changedInput schema / properties / query / description
      Previous value: -"Text to match in offering name, description, category, SKU, attributes, or business name/industry."New value: +"Literal search or supported phrases: three bedroom home near Nicosia under £500,000; property with 3 bedrooms in North Cyprus. Unsupported residual words remain literal constraints."
    • changedInput schema / properties / query / maxLength
      Previous value: -80New value: +300
  3. Changed3 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "Use next_cursor from the previous page (works at any depth).",
      +  "maxLength": 400,
      +  "type": "string"
      +}
    • changedInput schema / properties / offset / maximum
      Previous value: -1000New value: +100000
    • changedInput schema / properties / query / description
      Previous value: -"Text to match in offering name, description, category or business industry."New value: +"Text to match in offering name, description, category, SKU, attributes, or business name/industry."
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and open-world, so the safety profile is covered. The description adds genuine behavioral context beyond that: it returns applied criteria and stored match evidence, and explicitly never returns FX or distance estimates, which sets expectations about result content and limits.

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 dense sentence that front-loads the action and scope before the return-value caveat, with no wasted framing. Some phrasing ('stored match evidence', 'conservative buyer criteria') is abstract enough to be slightly opaque, but nothing is padded.

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

Completeness5/5

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

For a 12-parameter, optional-only read tool with no output schema, the description covers scope, eligible inventory, input style, and the exclusions on returned estimates. Pagination and limit details are fully documented in the schema, so no significant gap remains for correct invocation.

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 high (83%), so the schema already carries most parameter meaning, including alias handling, currency inference and bedroom semantics. The description adds only the high-level notion of 'literal keywords' versus 'conservative buyer criteria' and the no-FX/no-distance constraint, which is a baseline-level contribution.

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?

Names a specific verb ('Search') and a precisely scoped resource ('eligible published offers across AgentSynta'), plus the key discriminator 'without a slug' that separates it from a slug-based sibling search. It stops short of naming the alternative tool, so the differentiation is inferential rather than explicit.

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?

'Without a slug' and 'literal keywords or conservative buyer criteria' imply the conditions under which this tool applies, but there is no explicit when-to-use/when-not statement or named alternative (e.g. search_offerings). An agent must infer the routing rule.

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