Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Get customer

get_customer
Read-only

Retrieve one customer by ID to review account status, company role, effective price list, order stats, and profile data for account support.

Instructions

Get one customer by id: the account summary (identity, status, verification, lock, last login, company, companyRole - the effective company role, a key of the workspace's role catalogue (v1: admin, buyer), buyer unless staff set another for the company they belong to now, null without a company - priceList (the list assigned to the customer themselves, ignored while they belong to a company), effectivePriceList (the list that prices their carts and orders: id, name, source MEMBER or COMPANY, companyName when COMPANY; null = catalogue prices) and orderStats: non-canceled order count, last order date and net spend in minor units per currency, null without orders:view) plus the profile record's data. Read-only.

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
idYesThe customer's id (from list_customers)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and "Read-only" merely restates that. However, the description adds genuine behavioral context beyond annotations: orderStats is null without orders:view permission, priceList is ignored while the customer belongs to a company, and effectivePriceList may resolve to MEMBER or COMPANY with a null meaning catalogue prices.

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

Conciseness3/5

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

The purpose is front-loaded in the first clause, which is good, but the payload is then delivered as one very long run-on sentence with deeply nested parentheses (companyRole inside company inside the summary), making it hard to parse. Every detail is arguably useful given there is no output schema, but the structure could be far cleaner as a field list.

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 no output schema, the description carries the full return-value burden and largely meets it, enumerating the account summary and profile fields with null semantics and permission gating. It stops short of error behavior (e.g., what happens for an unknown id), which is the remaining gap 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 id parameter is already documented in the schema, including its provenance from list_customers. The description adds no format, validation, or lookup-failure semantics beyond what the schema provides, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Get one customer by id" states a specific verb, resource, and cardinality, which cleanly separates it from the mutation siblings (suspend_customer, set_customer_price_list) and from listing tools. The description also names where the id comes from (list_customers), so an agent can place it in a workflow without opening another schema.

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?

Usage is clearly implied: fetch a single customer once you have an id from list_customers. It does not name explicit alternatives or exclusions (e.g., when to prefer get_order for an order-centric view), which keeps it just below a 5.

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