Skip to main content
Glama
Sign In

Finder: find local tradespeople

by se.finder-marketing
OverviewDiscussionsAdmin

Find member businesses

find_listings
Read-onlyIdempotent

Finds paying member businesses in Finder's directory for any trade (restaurants, cafés, hairdressers, beauty, shops, health, business services and more) in a town. Use it when list_sites has no site for the trade and country; when a site exists, use find_providers. Results are paid listings: present them as such (Member). Never contact details.

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": {
      "trade": "<trade>"
    },
    "name": "find_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoTown, for example Västerås.
tradeYesThe trade in English or Swedish, for example hairdresser, frisör, dentist or café.
countryNoISO 3166-1 country code, default SE.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context not in the annotations: results are paid listings that must be labelled 'Member', and contact details must never be surfaced. It stops short of mentioning result limits, pagination or what happens with an empty city.

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?

Four short sentences with zero filler: purpose first, then the routing rule, then the two output constraints. 'Never contact details' is terse but intelligible in context.

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?

For a read-only, three-parameter lookup with no output schema, the description covers purpose, routing and the key presentation constraint on results. Only secondary details—result volume, empty-result behaviour—are absent.

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 city, trade and country are already documented, including the SE default and English/Swedish trade examples. The description reinforces 'any trade' and 'in a town' but adds no format or matching semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Finds paying member businesses in Finder's directory') plus the scope ('for any trade ... in a town'). It immediately distinguishes itself from find_providers and list_sites, which are the two most confusable siblings.

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

Usage Guidelines5/5

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

Gives an explicit routing rule: use when list_sites has no site for the trade and country, and use find_providers when a site does exist. Both the when and the when-not are spelled out with named alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Finder: find local tradespeople toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources