Skip to main content
Glama

Kartic

Search customers

search_customers
Read-only

Use when a signed-in merchant wants to find customers by name or phone. Requires owner or manager. Returns matching cards with stamp counts.

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
limitNo
queryYesName or phone fragment to search

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, closed-world behavior. The description adds useful context beyond them: it requires a signed-in merchant with owner or manager role and returns matching cards with stamp counts. It does not cover limit behavior or match semantics, but the added auth and result context is meaningful.

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?

The description is three short sentences, front-loaded with usage context and followed by prerequisites and return behavior. Every sentence adds useful information with no filler.

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 search tool with annotations covering safety and no output schema, the definition gives sufficient context: actor, permission, search fields, and return shape. It could be more complete by describing how limit affects results and whether matching is partial or exact.

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?

The schema already describes the required query parameter as a name or phone fragment. The description restates that query targets name or phone but adds no further meaning about the optional limit parameter, matching rules, or result ordering. With only 50% schema description coverage, this is adequate but does not compensate for the limit gap.

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 states a specific verb and resource (find customers by name or phone) and clarifies the merchant-facing context. It is clear enough to distinguish this from unrelated siblings like get_business_stats or send_wallet_notification, though it does not explicitly differentiate against any direct alternative search tool.

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

Usage Guidelines4/5

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

It gives explicit when-to-use guidance ('signed-in merchant wants to find customers by name or phone') and a permission prerequisite (owner or manager). It does not state when not to use it or name alternatives, but the context is clear.

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