Skip to main content
Glama

Rechercher une prestation

search_services
Read-onlyIdempotent

Recherche des prestations du catalogue Services (nom, référence, description) : identifiant, prix HT, TVA, unité, facteurs de calcul de la quantité, minimum facturé, tarifs dégressifs et options. (Lecture seule.)

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

Input Schema

NameRequiredDescriptionDefault
limitNoNombre maximum de prestations renvoyées (défaut 20).
queryNoVide = toutes les prestations actives

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so '(Lecture seule.)' merely restates structured data. The genuinely additive part is the enumeration of returned attributes, which compensates for the absence of an output schema and tells the agent what data comes back.

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?

A single front-loaded sentence with the resource named first, followed by the returned fields. The long attribute enumeration is justified because there is no output schema, and there is no filler wording.

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 search this covers what is retrieved and how the empty query behaves, which is adequate. What is missing is routing guidance relative to get_service and the other search_* tools, which the agent must infer from names alone.

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 description coverage is 100%: both 'limit' (default 20) and 'query' (empty = all active services) are already documented in the schema. The description adds no syntax, matching behavior or filtering semantics beyond that, so the baseline of 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?

States a specific verb ('Recherche') and resource ('prestations du catalogue Services'), and enumerates the data the records carry (identifiant, prix HT, TVA, unité, tarifs dégressifs, options). An agent can tell this apart from search_customers/search_products by the catalog named, though no sibling is explicitly contrasted.

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

Usage Guidelines2/5

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

No when-to-use guidance is given: nothing says when to search rather than call get_service, nor when to use a search tool at all versus a list tool. The only usage-like remark ('Vide = toutes les prestations actives') is parameter behavior, not tool selection guidance.

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