Skip to main content
Glama

Rechercher un client

search_customers
Read-onlyIdempotent

Recherche clients par nom/code/téléphone/email. (Lecture seule.)

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": {
      "query": "<query>"
    },
    "name": "search_customers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNombre maximum de clients renvoyés (défaut 10).
queryYesNom, code client, téléphone ou e-mail, même partiel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the parenthetical "(Lecture seule.)" merely restates structured data. The description adds no behavioral context beyond that, such as whether matching is case-insensitive, whether results are ordered, or how many matches are typical.

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?

Two very short clauses, front-loaded with the search fields, with zero filler. The only inefficiency is the redundant "(Lecture seule.)" parenthetical, which repeats the readOnlyHint annotation.

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 tool with full schema coverage and rich annotations, the description is adequate but thin. It never indicates what comes back (a list of customer records) or how to handle ambiguous/multiple matches, which matters since there is no output schema.

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%, so both `query` (name/code/phone/email, partial allowed) and `limit` (default 10) are already fully documented in the schema. The description echoes the query fields without adding semantics such as matching rules or result ordering, so the 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 gives a specific verb ("Recherche") plus the resource ("clients") and enumerates the searchable fields (nom/code/téléphone/email), so the agent knows exactly what the tool does. It does not explicitly distinguish itself from siblings such as get_customer or get_top_customers, so it stops short of a 5.

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?

Listing the matchable fields implicitly signals "use me when you have a partial name/code/phone/email rather than an identifier," which is a reasonable usage cue. However, there is no explicit when-to-use or when-not guidance and no named alternative (e.g., get_customer for exact ID lookups), leaving the agent to infer routing.

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