Skip to main content
Glama
Sign In

Agent Service Exchange

by io.github.PatrickPi1312
OverviewDiscussionsAdmin

Passende Dienstleister finden

find_service_providers
Read-onlyIdempotent

FREE. Finds voluntarily published business profiles for customers seeking tradespeople, cleaners or real-world services in an area. Qualifications are self-declared; no appointment is guaranteed. Country is ISO alpha-2; region is a coarse city/region name rather than a street address.

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>",
      "country": "<country>",
      "region": "<region>"
    },
    "name": "find_service_providers"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo
limitNo
tradeYes
regionYes
countryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, and closed-world. The description adds genuinely new behavioral context: results are voluntarily published, qualifications are self-declared, and no appointment is guaranteed, which tells the agent how much to trust the data. It stops short of describing result volume or how the returned profiles are shaped.

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?

Four short sentences with no filler, and the most decision-relevant facts, free and self-declared qualifications, come early. The final sentence is a dense two-fact clause but still readable; nothing is redundant.

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?

There is no output schema, so the description should say something about what a returned profile contains or how pagination via 'after' and 'limit' works; it does neither. It does cover data provenance and location precision well, making it adequate but incomplete for a five-parameter search tool.

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 0% across five parameters, so the description carries the burden. It explains two: country as ISO alpha-2 and region as a coarse city/region name rather than a street address. It says nothing about trade format, the meaning of 'after' (presumably a pagination cursor), or the behavior of 'limit', leaving three parameters undocumented in both sources.

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?

The description gives a specific verb and resource: it finds voluntarily published business profiles for tradespeople, cleaners, and other real-world services in an area. That is concrete enough to act on, but it does not name a sibling or contrast itself with closely named tools such as find_customer_job_requests or service_trade_catalog, so an agent must infer the boundary.

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?

The context is implied: this is the lookup you use when a customer needs a provider in a given area, and the leading 'FREE' hints at cost considerations. However, no when-to-use versus when-not guidance is given, and the description never routes the agent to alternatives like service_trade_catalog for trade validation or find_customer_job_requests for the inverse direction.

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

All Agent Service Exchange 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