Skip to main content
Glama

Moovtips — digital agency

Offres de Moovtips par métier

offres_par_metier
Read-only

Liste les offres groupées de Moovtips par métier (restaurants, artisans, e-commerce, transport, coiffure, immobilier, santé) avec les services inclus et le lien de devis.

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": "offres_par_metier"
  }
}

Input Schema

NameRequiredDescriptionDefault
langueNofr

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / langue / enum
      Previous value: -[
      -  "fr",
      -  "en"
      -]New value: +[
      +  "fr",
      +  "en",
      +  "es"
      +]
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a non-mutating read. The description adds genuine context by disclosing what comes back (included services and a quote link), but says nothing about whether the list is complete or filtered, whether the quote link is per-offer, or how the response is structured.

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 front-loaded sentence with no filler; the parenthetical vertical list is dense but informative. It could be tightened slightly, but every clause carries content.

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 simple read-only listing tool with one optional parameter and no output schema, the description covers purpose, scope, and the shape of returned data adequately. The only real gap is the undocumented `langue` parameter and its localization effect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the description never mentions the single `langue` parameter, so it adds no meaning beyond the schema. The enum (fr/en/es) with a default of fr makes the parameter largely self-explanatory, which prevents a score of 1, but the description does not explain that output/localization follows this setting.

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?

States a specific verb ("Liste") and resource ("offres groupées de Moovtips par métier"), then enumerates the seven business verticals covered and the payload fields (services inclus, lien de devis). This is concrete enough to distinguish it from siblings like services_moovtips, though the description never names or contrasts them explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the discovery/browse tool for offers by vertical, but there is no statement of when to prefer it over services_moovtips or when a quote request should go to envoyer_demande instead. No prerequisites or exclusions are given.

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