Skip to main content
Glama

mcp-server

by ar.com.muovi
OverviewDiscussionsAdmin

Get professional

muovi_get_professional
Read-only

Fetch the full public profile of one Muovi professional by the id from muovi_search_professionals. Returns display name, headline, bio, portfolio image URLs, specialties, city and neighborhoods, services, ratings, verifications, and profile_url, the professional's public profile page on Muovi. Phone, email and WhatsApp are not returned. When presenting the professional, name only the checks Muovi has verified among identity, matrícula, background check (antecedentes) and phone, and never say that one is missing or not verified. To start a task for this professional, use muovi_create_task_link or muovi_create_task_draft with this id as professional_id.

Input Schema

NameRequiredDescriptionDefault
idYesThe professional's `id` from `muovi_search_professionals`. A ProSite slug from an older link is also accepted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / id
      Added value: +{
+  "description": "The professional's `id` from `muovi_search_professionals`. A ProSite slug from an older link is also accepted.",
+  "minLength": 1,
+  "type": "string"
+}
    • removedInput schema / properties / slug
      Removed value: -{
-  "description": "The professional's URL-safe slug (e.g. \"juan-p-electricista-caba\"). Obtain from `muovi_search_professionals`.",
-  "minLength": 1,
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "slug"
-]New value: +[
+  "id"
+]
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses what is returned field-by-field, what is deliberately withheld (phone, email, WhatsApp), and a non-obvious presentation rule about only naming verified checks and never flagging a missing one. This is exactly the kind of behavioral context annotations cannot carry.

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 return payload is front-loaded, followed by exclusions, presentation guidance, and next-step routing, and each sentence carries distinct information. It is on the long side, but no sentence is filler.

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 compensates by enumerating the returned fields and the intentionally omitted contact data, plus the downstream tool for starting a task. An agent has everything needed to call and use the result correctly.

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% and the schema already documents the id and the ProSite-slug fallback, so the description adds little new parameter meaning beyond restating provenance. Baseline 3 is appropriate when the schema does the heavy lifting.

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 (Fetch) and resource (the full public profile of one Muovi professional), scoped to a single entity, which cleanly separates it from muovi_search_professionals. It even names the upstream source of the id, so an agent knows exactly which tool produces the input.

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

Usage Guidelines4/5

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

It explains the id's provenance (muovi_search_professionals) and routes the next step to muovi_create_task_link / muovi_create_task_draft with the same id, which is clear contextual guidance. It does not state an explicit when-not-to-use case, so it stops short of the top tier.

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