Skip to main content
Glama

Moovtips — digital agency

Lien du questionnaire de devis

lien_questionnaire
Read-only

Donne le lien du questionnaire de projet Moovtips avec les services déjà cochés, à transmettre à la personne si elle préfère remplir elle-même.

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>"
    },
    "name": "lien_questionnaire"
  }
}

Input Schema

NameRequiredDescriptionDefault
langueNofr
servicesYesIdentifiants des services voulus

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

A3.6/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe read, and the description usefully adds that the link comes pre-populated with the requested services and is meant for self-service. It does not say anything about link lifetime, what happens with an empty or very large service list, or how the response is shaped, which matters since there is no output schema.

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?

One compact sentence, front-loaded with the action and followed by the forwarding condition. Nothing is redundant, though the sentence is slightly dense.

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

Completeness3/5

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

For a two-parameter read-only tool without an output schema, the definition covers purpose and usage adequately but leaves the 'langue' parameter and the nature/validity of the returned link unaddressed. An agent could call it correctly but would not know what to expect from the language option.

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 50%: 'services' is documented in the schema, and the description reinforces it by explaining the values become pre-checked boxes in the questionnaire, which is genuine added meaning. The 'langue' parameter is never mentioned in the description and has no schema description, so its effect on the generated link is unexplained; with 50% coverage, that gap keeps this at a baseline 3.

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 states a concrete verb and resource: it returns the link to the Moovtips project questionnaire with the selected services pre-checked. That is specific enough to distinguish it from siblings like envoyer_demande or offres_par_metier, although it never names an alternative explicitly.

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 a clear usage condition: use it when the person prefers to fill the questionnaire themselves, and forward the link to them. The contrasting case (sending the request on their behalf, presumably via envoyer_demande) is only implied, not named.

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