Skip to main content
Glama

fixfind.at – local offers in Austria

Angebote suchen

search_offers
Read-onlyIdempotent

Search products and services offered by local businesses in Austria (mainly Vienna and Lower Austria) listed on fixfind.at. Listings are in German, so use German search terms (e.g. "Möbelmontage", "Fotograf", "Felgenreparatur"). Filter by location (Austrian postal code like "1100", a prefix like "23", or a town name like "Mödling"), category and maximum price. Call without arguments to browse all offers. Returns short summaries; use get_offer for full details. Always give the user the offer url.

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_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results to return (1-25).
queryNoGerman search terms, e.g. "Umzug Wien" or "Passfoto". Optional.
offsetNoFor paging through results.
categoryNoExact category. Optional.
locationNoAustrian postal code (4 digits), postal code prefix, or town name. Optional.
max_priceNoMaximum price in EUR. Excludes offers without a price. Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"Number of results to return (1-25)."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so safety is covered. The description still adds real value beyond them: listings are German-language, results are short summaries rather than full records, and there is a downstream obligation to surface the offer URL. Pagination behavior via limit/offset is only implied.

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 paragraph that front-loads what the tool does before listing filters and the sibling handoff. Nearly every sentence earns its place; the trailing instruction about handing the user the offer URL is a workflow note rather than tool selection info, but it is short and useful.

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 correctly fills the gap by saying results are short summaries and pointing at get_offer for full records. Six optional parameters, filtering and browsing are all covered. It stops short of explaining pagination limits or result ordering, which would be minor additions.

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 coverage is 100%, so the schema already documents limit, query, offset, category, location and max_price, including the enum values. The description adds only soft guidance (German terms with examples, flexible location formats) that largely duplicates what the schema says. Baseline 3 applies when the schema carries the detail.

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 specific verb and resource with scope: products and services from local businesses in Austria (Vienna/Lower Austria) on fixfind.at. It cleanly separates itself from get_offer, which it names for full details. The one gap is that it never distinguishes itself from the sibling search_products, so an agent has to guess which search endpoint covers offers vs. products.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete when-to-use guidance: call with no arguments to browse everything, use German search terms with examples, and switch to get_offer for details. It lacks an explicit when-not-to-use statement or a pointer to search_products, which is the only real ambiguity left.

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