Skip to main content
Glama

Find customer

find_customer
Read-only

Retrieve a customer record by email to view plan, monthly payment, account status, and signup date. Use it to answer questions about individual accounts.

Instructions

Find a customer by email and show their plan, monthly payment, status and signup date.

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": {
      "email": "<email>"
    },
    "name": "find_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesThe customer's email, for example riya@example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description does add value by previewing the returned fields in the absence of an output schema, but it says nothing about behavior on a miss (error vs empty result) or about matching exactness.

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?

A single front-loaded sentence with zero padding; the key, the result fields, and the purpose all land in one pass.

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 annotations covering safety, the definition is nearly sufficient, and the returned-field preview compensates for the missing output schema. The notable gap is not-found behavior, which an agent calling with arbitrary emails would benefit from knowing.

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?

One parameter with 100% schema description coverage, so the schema already documents the email argument and gives an example. The description adds no semantics beyond 'by email' — no indication of case sensitivity, normalization, or whether partial matches are accepted.

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 (find), resource (customer), lookup key (email), and the fields returned (plan, monthly payment, status, signup date). This makes it clearly the single-customer lookup rather than an aggregate like revenue_summary or signups_this_week, though it never explicitly contrasts itself with those siblings.

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?

The only guidance is the lookup key implied by 'by email'; there is no statement of when to prefer this over the sibling reporting tools, no prerequisites (auth/scope), and no handling guidance when no customer matches.

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

Deploy Server

Other Tools