Skip to main content
Glama

mcp-server

by ar.com.muovi

Search professionals

muovi_search_professionals
Read-only

Search for verified service professionals in Argentina by service type, city, neighborhood, verification status, minimum rating, and minimum review count. Returns a paginated list of professionals with display name, headline, ratings, verifications, and a profile_url that is the only sanctioned contact channel (no phone/email/whatsapp is ever returned). Use this for discovery; use muovi_get_professional for the full detail payload.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity slug (e.g. "caba"). Matches `City.slug` in the catalog.
limitNoMaximum number of results per page (default 20, max 50).
offsetNoZero-based offset into the result set for pagination.
serviceNoService slug (e.g. "electricidad"). Matches `Service.slug` in the catalog.
min_ratingNoMinimum blended average rating, 0-5 inclusive.
min_reviewsNoMinimum blended review count.
neighborhoodNoNeighborhood slug (e.g. "palermo"). Matches `Neighborhood.slug` in the catalog.
has_matriculaNoWhen true, only return pros with a verified professional matrícula on file (electricians, gas fitters, etc.).
verified_identityNoWhen true, only return pros whose identity has been verified by Muovi.

TDQS

A4.9/5.0
Behavior5/5

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

Annotations provide readOnlyHint and openWorldHint. The description adds that results are paginated, lists returned fields, and clarifies that no phone/email/whatsapp is ever returned and that profile_url is the only sanctioned contact channel. No contradiction with annotations.

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?

Just two sentences: first sentence covers purpose, filters, and output; second sentence gives usage guidance and contact channel. Every word earns its place with no redundancy.

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?

Given 9 parameters, no output schema, and no enums, the description covers the essential purpose, filters, return fields, pagination, and usage guidance. It is complete for an agent to decide when and how to use this tool.

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 description coverage is 100%, so baseline is 3. The description adds value by summarizing the filter parameters and mentioning the return fields, providing a holistic understanding beyond individual schema descriptions.

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 clearly states the verb 'Search', the resource 'verified service professionals', and the scope 'in Argentina by service type, city, neighborhood, verification status, minimum rating, and minimum review count.' It also distinguishes from sibling 'muovi_get_professional' by specifying discovery vs. detail payload.

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?

Explicitly states when to use this tool ('Use this for discovery') and when to use the alternative ('use muovi_get_professional for the full detail payload'). Also notes the only sanctioned contact channel and that phone/email/whatsapp are never returned.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: generating deep links, fetching professional profiles, reviews, listing cities and services, and searching professionals. No overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent 'muovi_verb_noun' snake_case pattern (e.g., muovi_search_professionals, muovi_list_cities), making it predictable.

Tool Count5/5

Six tools cover the necessary operations for a service professional platform without being excessive or insufficient. Each tool serves a clear need.

Completeness5/5

The tool set covers discovery (search, list cities/services), detailed information (professional, reviews), and the intended action (deep link for task creation). The lack of server-side task creation is by design, so the surface is complete.

Resources