Skip to main content
Glama

Washlib

by com.washlib
OverviewDiscussionsAdmin

Trouver des centres

find_centers
Read-onlyIdempotent

Active car-wash centres near a place, nearest first, from the place as the customer names it (city, district, postal code or centre name). resolvedLocation reports how the place was understood.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationYesWhere the customer wants the wash: city, district, postal code or centre name, e.g. "Paris 16", "Levallois", "75017"
radiusKmNoSearch radius in kilometres (default 20, max 50)
serviceTypeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / latitude
      Removed value: -{
-  "description": "Only a REAL position shared by the user — never a guess",
-  "maximum": 90,
-  "minimum": -90,
-  "type": "number"
-}
    • changedInput schema / properties / location / description
      Previous value: -"Where the customer is or wants the wash, in their words: city, district, postal code, address or centre name, e.g. \"Paris 16\", \"Levallois\", \"75017\". Preferred over coordinates."New value: +"Where the customer wants the wash: city, district, postal code or centre name, e.g. \"Paris 16\", \"Levallois\", \"75017\""
    • removedInput schema / properties / longitude
      Removed value: -{
-  "maximum": 180,
-  "minimum": -180,
-  "type": "number"
-}
    • addedInput schema / required
      Added value: +[
+  "location"
+]
  2. Changed4 schema fields changed
    • addedInput schema / properties / latitude / description
      Added value: +"Only a REAL position shared by the user — never a guess"
    • addedInput schema / properties / location
      Added value: +{
+  "description": "Where the customer is or wants the wash, in their words: city, district, postal code, address or centre name, e.g. \"Paris 16\", \"Levallois\", \"75017\". Preferred over coordinates.",
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / properties / radiusKm / description
      Previous value: -"Search radius in kilometres (max 50)"New value: +"Search radius in kilometres (default 20, max 50)"
    • removedInput schema / required
      Removed value: -[
-  "latitude",
-  "longitude",
-  "radiusKm"
-]
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, so the bar is lower, and the description still adds real behavior: only active centres are returned, results are sorted nearest-first, and resolvedLocation explains location interpretation. It stops short of describing the returned record shape.

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?

Two short sentences, fully front-loaded: the sorting and filter behavior comes first, with the resolvedLocation note as a compact follow-up. No wasted words.

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 three-parameter, read-only discovery tool with no output schema, the description should say more about what comes back (record fields, pagination, limits). It covers ordering, the active filter, and one response field, but leaves the serviceType parameter and the result shape unexplained.

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 67%. The description reinforces the flexible location semantics (city, district, postal code or centre name), duplicating the schema's own text, but adds nothing for serviceType, whose fixed/mobile/home enum values are unexplained in both schema and description. Baseline 3 fits.

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+resource ('car-wash centres') with scope qualifiers: 'Active', 'near a place', 'nearest first'. This is clearly distinguishable from get_center_details or search_available_slots, though no sibling is named explicitly.

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 implied by the description (find active centres near a place), and it hints that the location is 'the place as the customer names it', but it never states when to prefer this over siblings like get_center_details or what conditions exclude it.

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

All Washlib 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