Skip to main content
Glama

Fiche client

get_customer
Read-onlyIdempotent

Détails client + 5 dernières factures. (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": {
      "id": "<id>"
    },
    "name": "get_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIdentifiant du client.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the parenthetical read-only note adds nothing new. The one genuinely additive fact is that a single call also returns the last five invoices, which is useful disclosure about response breadth.

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 short, front-loaded fragments with the highest-value information first — what comes back and how much. The trailing '(Lecture seule.)' duplicates readOnlyHint from the annotations and is the only expendable text.

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 one-parameter read tool with no output schema, the description covers the essentials: it names the resource and the contents of the response. Only edge-case behavior (missing customer, identifier type expectations) is unaddressed.

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?

There is a single required parameter with 100% schema description coverage, so the schema already defines id as the customer identifier. The description adds nothing beyond that (no format, id-space distinction, or error semantics), making the baseline 3 correct.

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 resource (customer record) and discloses the composite payload — details plus the five most recent invoices — which an agent could not infer from the name alone. It stops short of differentiating itself from neighboring retrieval tools such as get_top_customers or get_invoice, so it does not reach 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?

Usage is only implied by the name and the id parameter: fetch one customer's file. There is no statement of when to prefer this over a list/summary sibling, and no note on what happens with an unknown id. The '(Lecture seule.)' note is context, not 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