Skip to main content
Glama
BenjaminJ

enterprise-mcp-gateway

by BenjaminJ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

getCustomerDetails

Retrieve a customer's full account profile using an exact customer ID, including tax ID, billing address, service tier, and primary contact details. Provides read-only access without side effects.

Instructions

Retrieve full profile record for a specific customer by ID - Retrieves comprehensive account profile metadata for an individual enterprise customer.

[Usage Guidelines]

  • When to use: Use this tool when you have an exact customerId and need full profile information such as registered tax ID, billing address, account tier, and primary contact details.

  • When NOT to use: Do NOT use this tool to search or discover customers; use 'listCustomers' instead. Do NOT use to view invoices or payment methods; use 'getBillingHistory' instead.

  • Prerequisites: Requires a valid 'customerId' (format 'cust-XXX') previously obtained via 'listCustomers'.

[Behavior]

  • Operation: Read-only and idempotent. Calling this tool causes no mutations or side effects.

  • Authorization: Requires 'readonly_agent', 'support_agent', or 'admin' role.

  • DLP / Sanitization: Sensitive personal attributes (such as SSN or tax identifiers) are automatically masked by the gateway DLP engine before response delivery.

[Parameters]

  • 'customerId' (path, required): Unique customer identifier string in 'cust-XXX' format (e.g. 'cust-001'). Must match an existing customer record.

[Returns]

  • Returns HTTP 200 with full customer profile: customerId, name, email, taxId (redacted), address, serviceTier, and status. Returns HTTP 404 if the customerId does not exist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customerIdYesUnique customer identifier in format 'cust-XXX' (e.g., 'cust-001', 'cust-002'). Must correspond to an existing customer record discovered via listCustomers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.3
    • changedInput schema / properties / customerId / description
      Previous value: -"Unique customer identifier in format 'cust-XXX' (e.g., 'cust-001', 'cust-002')."New value: +"Unique customer identifier in format 'cust-XXX' (e.g., 'cust-001', 'cust-002'). Must correspond to an existing customer record discovered via listCustomers."
  2. Changed2 schema fields changedv1.0.1
    • changedInput schema / properties / customerId / description
      Previous value: -"Unique customer identifier"New value: +"Unique customer identifier in format 'cust-XXX' (e.g., 'cust-001', 'cust-002')."
    • addedInput schema / properties / customerId / example
      Added value: +"cust-001"
  3. First observedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so thoroughly: it declares the operation is read-only and idempotent, lists required authorization roles, and discloses DLP redaction of sensitive identifiers. This is strong behavioral disclosure beyond the bare schema.

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

Conciseness4/5

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

The description is well-organized with clear headings and front-loaded purpose. There is some redundancy between the opening sentence and the usage/returns sections, but overall every major section earns its place and the structure supports quick scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given there is no output schema and no annotations, the description compensates completely: it covers when to use, when not to use, prerequisites, behavior, authorization, DLP sanitization, parameter semantics, return payload, and error status. Nothing an agent needs to call it correctly is missing.

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 description coverage is 100%, so the baseline is 3. The tool description adds the path-binding detail and restates the 'cust-XXX' format and existence requirement, but most parameter meaning is already present in the schema. It adds value only marginally.

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?

The description states a specific verb and resource: 'Retrieve full profile record for a specific customer by ID'. It clearly frames the tool as returning account profile metadata for one enterprise customer, which differentiates it from list-oriented or billing-related siblings.

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

Usage Guidelines5/5

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

Explicit 'When to use' and 'When NOT to use' sections name alternatives (listCustomers, getBillingHistory) and the conditions for choosing them. It also states the prerequisite of having a valid customerId from listCustomers, leaving no ambiguity about when the tool applies.

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