Skip to main content
Glama

Moovtips — digital agency

Services de Moovtips

services_moovtips
Read-only

Liste les services de l'agence digitale Moovtips (sites web 3D, Shopify, SEO, agent vocal IA, contenu UGC, publicité Meta/Google, automatisations IA, flyers, cartes de visite et magnets, identité visuelle, flyers / cartes de visite / magnets), avec la page de chaque service et le lien de devis. Utilise-le quand une personne cherche l'un de ces services.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "services_moovtips"
  }
}

Input Schema

NameRequiredDescriptionDefault
langueNoLangue de la personne (fr, en ou es)fr

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / langue / description
      Previous value: -"Langue de la personne"New value: +"Langue de la personne (fr, en ou es)"
    • changedInput schema / properties / langue / enum
      Previous value: -[
      -  "fr",
      -  "en"
      -]New value: +[
      +  "fr",
      +  "en",
      +  "es"
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real value by disclosing the payload shape (each service's page plus the quote link), but says nothing about whether results are filtered by language, ordering, or size of the list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in one sentence, which is good. However the service enumeration is padded and partially duplicated — "flyers, cartes de visite et magnets" appears twice inside the same parenthesis — which is wasted space in an otherwise short description.

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 zero-required-parameter, read-only listing tool with no output schema, the definition covers what it does, when to use it, and roughly what comes back, which is sufficient. The one omission is how the langue parameter affects the returned content.

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% with a single optional enum parameter (langue, fr/en/es) already documented in the schema. The description never mentions that output language depends on this parameter, so it adds no meaning beyond the schema; baseline 3 applies.

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 ("Liste les services de l'agence digitale Moovtips") and enumerates the actual service categories, so an agent knows exactly what corpus is returned. It stops short of naming a sibling to contrast with (e.g. offres_par_metier, which sounds closely related), leaving the boundary to be inferred.

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?

"Utilise-le quand une personne cherche l'un de ces services" gives an explicit positive trigger tied to the enumerated list. There are no exclusion conditions or named alternatives for the near-neighbour tools, which is the only gap.

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