Skip to main content
Glama

mcp-server

Create task draft

muovi_create_task_draft

Save a task draft on Muovi for the person you are helping, and get back a link for them. The person opens the link, reviews the draft, signs in to Muovi and publishes it themselves. This tool publishes nothing and does not notify any professional. To hand over the full request, call muovi_get_service_requirements for the service first and collect the required fields it lists, asking one question per message and waiting for the answer before asking the next. A draft whose urgency is flexible is complete without the date. Also ask what a professional would need to quote this specific job, skip anything the person already said, and write those details into description; no list of job questions is prescribed. Send the answers in slots (keyed by slot key) with location. Do not ask the optional slots as a list; when what the person has told you, at any point in the conversation, gives an optional slot's value, send it in slots as well as writing it in description. If a required answer is missing, the result has status: "incomplete", lists the questions still to ask and carries no link: ask them one per message and call again with every answer. If a value is not accepted, the result has status: "invalid_slots" and names each slot. A draft with every required answer opens on a review form with those answers filled in, without asking them again, unless Muovi's assistant has a question of its own for the person, and the person confirms the address on Muovi's map after opening the link, before publishing. Sending only description still saves a draft, and that link opens Muovi's assistant, which asks the person its questions. To direct the draft to one professional, pass professional_id, the id of any result from muovi_search_professionals: when the person publishes it, the task goes to that professional first for 24 hours and then opens to everyone, unless open_to_others is true, in which case it opens to everyone right away and that professional is still told. Set open_to_others from what the person chose; they can change it on the review form. A ProSite slug in professional_slug is still accepted instead of professional_id. Leave both out for a general request to get offers from several professionals. service_slug comes from muovi_list_services. A link nobody has opened expires 24 hours after it is created. The first person to open it takes the draft, signed in or not, and can reopen the link for up to 7 days, so give it only to that person. Do not include phone numbers, email addresses or other contact details in any text.

Input Schema

NameRequiredDescriptionDefault
slotsNoOptional. The person's answers, keyed by slot key from `muovi_get_service_requirements`. Send each value in the slot's `value_format`.
titleNoOptional. A short title for the task, 5 to 80 characters. Left out, Muovi takes it from the description.
locationNoOptional. Where the job is: `neighborhood_slug`, `address`, or both. The address is saved as text; the person confirms the place on the map on Muovi.
zone_textNoOptional. Where the job is, as free text (neighborhood or area), up to 120 characters.
descriptionYesWhat the person needs done, in their words, with the job details a professional would need to quote it: 20 to 2000 characters.
service_slugYesThe service slug (from `muovi_list_services`), e.g. "electricidad".
budget_amountNoOptional. The person's budget in ARS, as a positive number.
open_to_othersNoOptional, with professional_id. True when the person also wants offers from other professionals right away; false or omitted gives the chosen professional the first 24 hours.
preferred_dateNoRequired with preferred_time "specific_date", otherwise omitted. YYYY-MM-DD, from today up to 90 days ahead (Argentina time).
preferred_timeNoOptional. When the person wants it done. Use "specific_date" together with `preferred_date`.
professional_idNoOptional. The `id` of a professional from `muovi_search_professionals` to direct the draft to. Omit for a general request.
time_preferencesNoOptional. The parts of the day that suit the person.
professional_slugNoOptional. A ProSite slug from an older link, instead of professional_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / description / description
      Previous value: -"What the person needs done, in their words: 20 to 2000 characters."New value: +"What the person needs done, in their words, with the job details a professional would need to quote it: 20 to 2000 characters."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true. The description goes far beyond them: it discloses that nothing is published or notified, that incomplete/invalid input returns status 'incomplete' or 'invalid_slots' with no link, that an unopened link expires in 24 hours, that the first opener takes the draft and can reopen for 7 days, and that contact details must be excluded.

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 purpose and the publish-nothing guarantee are front-loaded, and nearly every sentence carries operational information for a 13-parameter tool. It is a dense, run-on paragraph without headings or bullets, which hurts scannability, but little of the content 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?

For a complex 13-parameter mutation with no output schema, nested objects, and an interactive collection workflow, the description covers prerequisites, the interactive ask-loop, error statuses, link lifecycle, and privacy constraints. An agent has essentially everything needed to drive the flow correctly.

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 meaning: professional_id vs professional_slug equivalence, that open_to_others controls whether the chosen professional gets a 24-hour head start, that slots are keyed by slot key from muovi_get_service_requirements, and that a 'flexible' urgency needs no date.

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 first sentence states a precise verb and resource ('Save a task draft on Muovi ... and get back a link') and immediately clarifies the crucial distinction that it publishes nothing, which separates it from a link/publication flow. An agent can tell what this tool does and what it does not do without opening the 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?

The description routes the agent explicitly: call muovi_get_service_requirements first and collect its fields, use muovi_list_services for service_slug, muovi_search_professionals for professional_id, and leave both professional fields out for a general request. It also gives when-to-use rules for open_to_others and the one-question-per-message protocol.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources