Skip to main content
Glama

mcp-server

by ar.com.muovi
OverviewDiscussionsAdmin

Search professionals

muovi_search_professionals
Read-only

Find up to 5 Muovi professionals for one service in one barrio. Both service (a slug from muovi_list_services) and neighborhood (a barrio slug from muovi_list_cities) are required: if the person has not said which service they need and in which barrio, ask them before searching. Every professional returned has a coverage area that includes the searched barrio, and match in the response names the service, barrio and city searched: present the results as professionals who work in that barrio. Results list professionals who declare the searched trade first, ordered by review score, with verified identity, background check and matrícula counting toward it; professionals whose registered business is in another trade come last. Each result has one rating and one review_count, and verifications: for each professional, say whether identity, matrícula, background check (antecedentes) and phone are verified. Each result also has up to 3 portfolio image URLs, an id and a profile_url, the professional's public profile page on Muovi; no phone, email or WhatsApp is returned. After showing the results, offer the person two choices: a task for one professional (muovi_create_task_link, or muovi_create_task_draft with professional_id, passing that result's id), or a general request to get offers from several professionals (muovi_create_task_draft without a professional). Use muovi_get_professional with the id for the full profile.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoOptional. City slug (e.g. "caba"), needed only when a barrio slug exists in more than one city.
serviceYesRequired. Service slug (e.g. "plomeria"), from `muovi_list_services`.
neighborhoodYesRequired. Barrio slug (e.g. "palermo"), from `muovi_list_cities`.
has_matriculaNoWhen true, only return professionals with a verified matrícula on file (electricians, gas fitters, etc.).
verified_identityNoWhen true, only return professionals whose identity Muovi has verified.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • changedInput schema / properties / city / description
      Previous value: -"City slug (e.g. \"caba\"). Matches `City.slug` in the catalog."New value: +"Optional. City slug (e.g. \"caba\"), needed only when a barrio slug exists in more than one city."
    • changedInput schema / properties / has_matricula / description
      Previous value: -"When true, only return pros with a verified professional matrícula on file (electricians, gas fitters, etc.)."New value: +"When true, only return professionals with a verified matrícula on file (electricians, gas fitters, etc.)."
    • removedInput schema / properties / limit
      Removed value: -{
-  "description": "Maximum number of results per page (default 20, max 50).",
-  "maximum": 50,
-  "minimum": 1,
-  "type": "integer"
-}
    • removedInput schema / properties / min_rating
      Removed value: -{
-  "description": "Minimum blended average rating, 0-5 inclusive.",
-  "maximum": 5,
-  "minimum": 0,
-  "type": "number"
-}
    • removedInput schema / properties / min_reviews
      Removed value: -{
-  "description": "Minimum blended review count.",
-  "minimum": 0,
-  "type": "integer"
-}
    • changedInput schema / properties / neighborhood / description
      Previous value: -"Neighborhood slug (e.g. \"palermo\"). Matches `Neighborhood.slug` in the catalog."New value: +"Required. Barrio slug (e.g. \"palermo\"), from `muovi_list_cities`."
    • removedInput schema / properties / offset
      Removed value: -{
-  "description": "Zero-based offset into the result set for pagination.",
-  "minimum": 0,
-  "type": "integer"
-}
    • changedInput schema / properties / service / description
      Previous value: -"Service slug (e.g. \"electricidad\"). Matches `Service.slug` in the catalog."New value: +"Required. Service slug (e.g. \"plomeria\"), from `muovi_list_services`."
    • changedInput schema / properties / verified_identity / description
      Previous value: -"When true, only return pros whose identity has been verified by Muovi."New value: +"When true, only return professionals whose identity Muovi has verified."
    • addedInput schema / required
      Added value: +[
+  "service",
+  "neighborhood"
+]
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses the 5-result cap, ordering rules (declared trade first, then review score, verified identity/background/matrícula weighting, other-trade businesses last), the presence of a match echo, and the privacy fact that no phone, email or WhatsApp is returned. This is behavior an agent cannot infer from structured fields.

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?

The required-inputs rule is front-loaded and every paragraph carries actionable content, but the middle section on ordering and verification fields is dense and slightly repetitive for a single tool description. Still efficient enough to justify its length given the absence of an output schema.

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?

With no output schema, the description fully documents the return shape (match, rating, review_count, verifications, up to 3 portfolio URLs, id, profile_url) and the next-step workflow, so an agent has everything needed to call the tool and act on the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantics: it ties service and neighborhood to their slug-producing tools and to the requirement to ask the user when missing, and explains city's optional disambiguation role implicitly. The has_matricula and verified_identity filters are left to the schema, so it does not fully compensate beyond baseline.

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?

The description opens with a precise verb+resource+scope: find up to 5 professionals for one service in one barrio. It clearly separates this from siblings such as muovi_get_professional (full profile) and muovi_create_task_draft (next step), so an agent can route correctly without reading any schema.

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?

It states both required inputs and their slug sources, instructs the agent to ask the user before searching when service or barrio is unknown, and explicitly routes post-search follow-ups to muovi_create_task_link, muovi_create_task_draft (with or without professional_id) and muovi_get_professional. Alternative conditions are spelled out rather than implied.

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

All mcp-server 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