Skip to main content
Glama
mcp-erp-server

mcp-erp-server

by aldemarluz

Find customer

sales_find_customer
Read-only

Search customers by name, ID, or tax ID and return tier and city to identify the right account.

Instructions

Search customers by name, id or tax id. Returns tier and city.

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

Input Schema

NameRequiredDescriptionDefault
queryYesPart of the name, the id or the tax id

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?

The readOnlyHint annotation already establishes that this is a safe read, so the description's main added value is disclosing partial return content ('tier and city'). With no output schema present, it does not say whether one match or many are returned, whether the result is truncated, or what happens on zero hits.

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 tight sentences with the search capability front-loaded and the return hint trailing; nothing is redundant 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?

For a one-parameter read-only lookup this covers the essentials and even gestures at return fields. The only shortfall is the absence of any note on result cardinality or empty-result behavior, which would matter for a lookup tool.

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 coverage is 100% and the single parameter is already documented as 'Part of the name, the id or the tax id', so the description's phrasing adds little beyond the schema. Baseline 3 applies since the schema carries the parameter semantics.

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 concrete verb and resource - 'Search customers' - and enumerates the lookup keys (name, id, tax id). It distinguishes itself adequately from the listed siblings, none of which deal with customer records, though it never explicitly routes the agent away from any alternative.

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?

There is no statement of when to use this tool versus not, no prerequisites, and no note about what to do when a lookup fails or returns multiple matches. The only implied guidance is the partial-match nature of the search keys.

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