Skip to main content
Glama

Moovtips — digital agency

Envoyer une demande de devis à Moovtips

envoyer_demande

Envoie une demande de devis à Moovtips au nom de la personne. Avant de l'appeler : demande-lui son prénom, le nom de son entreprise, son e-mail, son métier, sa ville et son besoin (sans rien inventer), puis demande-lui explicitement si elle accepte que ces informations soient transmises à Moovtips. Moovtips répond sous 48 heures.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "services": "<services>",
      "prenom": "<prenom>",
      "entreprise": "<entreprise>",
      "email": "<email>",
      "metier": "<metier>",
      "ville": "<ville>",
      "besoin": "<besoin>",
      "consentement": "<consentement>"
    },
    "name": "envoyer_demande"
  }
}

Input Schema

NameRequiredDescriptionDefault
delaiNo
emailYes
villeYesVille ou zone des clients
besoinYesLe besoin décrit par la personne, avec ses mots
budgetNo
langueNofr
metierYesCe que fait l'entreprise
prenomYes
servicesYesServices voulus (voir services_moovtips)
telephoneNoDe préférence le numéro WhatsApp
entrepriseYes
consentementYestrue seulement si la personne a accepté explicitement que ses informations soient transmises à Moovtips

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / services / items / enum
      Previous value: -[
      -  "site-vitrine",
      -  "site-3d",
      -  "standard-ia",
      -  "seo",
      -  "ugc",
      -  "shopify",
      -  "publicite",
      -  "automatisation",
      -  "identite",
      -  "print",
      -  "video-ia",
      -  "maintenance",
      -  "chat-ia",
      -  "reservation",
      -  "application",
      -  "reseau",
      -  "cybersecurite",
      -  "infogerance"
      -]New value: +[
      +  "site-vitrine",
      +  "site-3d",
      +  "standard-ia",
      +  "seo",
      +  "ugc",
      +  "shopify",
      +  "publicite",
      +  "automatisation",
      +  "identite",
      +  "print",
      +  "video-ia",
      +  "maintenance",
      +  "chat-ia",
      +  "reservation",
      +  "application",
      +  "reseau",
      +  "cybersecurite",
      +  "infogerance",
      +  "fichier-contacts",
      +  "prospection"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / langue / enum
      Previous value: -[
      -  "fr",
      -  "en"
      -]New value: +[
      +  "fr",
      +  "en",
      +  "es"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / services / items / enum
      Previous value: -[
      -  "site-vitrine",
      -  "site-3d",
      -  "standard-ia",
      -  "seo",
      -  "ugc",
      -  "shopify",
      -  "publicite",
      -  "automatisation",
      -  "identite",
      -  "print",
      -  "video-ia",
      -  "maintenance",
      -  "chat-ia",
      -  "reservation"
      -]New value: +[
      +  "site-vitrine",
      +  "site-3d",
      +  "standard-ia",
      +  "seo",
      +  "ugc",
      +  "shopify",
      +  "publicite",
      +  "automatisation",
      +  "identite",
      +  "print",
      +  "video-ia",
      +  "maintenance",
      +  "chat-ia",
      +  "reservation",
      +  "application",
      +  "reseau",
      +  "cybersecurite",
      +  "infogerance"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / services / items / enum
      Previous value: -[
      -  "site-3d",
      -  "standard-ia",
      -  "seo",
      -  "ugc",
      -  "shopify",
      -  "publicite",
      -  "automatisation",
      -  "identite"
      -]New value: +[
      +  "site-vitrine",
      +  "site-3d",
      +  "standard-ia",
      +  "seo",
      +  "ugc",
      +  "shopify",
      +  "publicite",
      +  "automatisation",
      +  "identite",
      +  "print",
      +  "video-ia",
      +  "maintenance",
      +  "chat-ia",
      +  "reservation"
      +]
  5. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description does real work: it discloses that this is an outbound transmission of personal data to a third party, that consent must be explicit first, and that the partner replies within 48 hours. It stops short of describing failure handling, whether a submission can be revoked, or any rate limits, which keeps it from a 5.

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 is front-loaded in one sentence, followed by a compact operational instruction and a single expectation-setting clause. Nothing is redundant, though the middle sentence is a dense run-on list rather than being broken into shorter, scannable steps.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter write tool with no annotations and no output schema, the description covers the essentials an agent needs: required data, no fabrication, explicit consent, and expected turnaround. It leaves the services enum and the optional fields (téléphone, budget, langue, delai) unexplained, which is the main residual gap.

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?

At 50% schema coverage over 12 parameters, the description compensates well by naming 7 of the 8 required fields and stressing that besoin must be captured 'sans rien inventer' and that consentement means real agreement. It says nothing about services (the enum array), telephone, budget, delai or langue, so the optional half of the schema is left entirely to the schema.

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?

The description opens with a specific verb and resource: 'Envoie une demande de devis à Moovtips au nom de la personne', which makes the action and the actor unambiguous. It does not explicitly contrast with the siblings (services_moovtips, lien_questionnaire, offres_par_metier), but those names suggest different purposes, so an agent can still pick correctly.

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 gives clear preconditions for use: collect prénom, entreprise, email, métier, ville and besoin from the person, invent nothing, and obtain explicit consent before calling. It never names an alternative tool or states when not to use this one, so route-level guidance is implied rather than explicit.

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