Skip to main content
Glama

find_customer

Read-onlyIdempotent

Search customers by partial name, email, or ID to retrieve city, order count, and total spent.

Instructions

Busca clientes por parte do nome, e-mail ou ID. Retorna cidade, nº de pedidos e total gasto.

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

Input Schema

NameRequiredDescriptionDefault
queryYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered without prose. The description adds one genuine behavioral trait — partial ('por parte do nome') matching — but the listed return fields (cidade, nº de pedidos, total gasto) largely restate what the output schema already provides.

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

Conciseness5/5

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

Two short sentences with zero filler, with the search scope front-loaded before the return values. Nothing is repeated or padded.

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?

With an output schema present, the description needn't detail return values, and annotations cover the safety profile, so what remains is appropriately light. The only real gap is matching semantics — substring vs prefix, case handling, and what happens when multiple customers match.

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

Parameters4/5

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

The single parameter has 0% schema description coverage, so the description carries the burden: it tells the agent that 'query' accepts a name fragment, an email, or an ID. That is meaningful semantics beyond the bare 'string' schema, though it omits case-sensitivity, minimum length, and multi-match behavior.

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 and resource ('Busca clientes') plus the three match fields (nome, e-mail, ID), which tells an agent exactly what this retrieval is keyed on. It stops short of naming how it differs from siblings like customer_orders, but the lookup-vs-order-listing distinction is inferable from the fields named.

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: the description makes clear this is the lookup path when you have a partial name, an email, or an ID. There is no explicit when-to-use/when-not statement, no mention of prerequisites, and no alternative named when several customers could match.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.