Skip to main content
Glama

Get Customer Tool

get-customer
Read-only

Returns one authorized customer using bounded contact and lifecycle fields; addresses and notes are excluded. Use to get customer in the connected business. Returns customer, related_jobs, scope.

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": {
      "customer_id": "<customer_id>"
    },
    "name": "get-customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
customer_idYesCustomer ID returned by search-customers.

Output Schema

NameRequiredDescriptionDefault
scopeYesAuthorization scope of this result; data remains restricted to the connected business.
customerYesCustomer data returned by the authorized safe projection.
related_jobsYesBounded related jobs records returned by this tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / required
      Added value: +[
      +  "customer_id"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "customer": {
      +      "description": "Customer data returned by the authorized safe projection.",
      +      "type": "object"
      +    },
      +    "related_jobs": {
      +      "description": "Bounded related jobs records returned by this tool.",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "scope": {
      +      "description": "Authorization scope of this result; data remains restricted to the connected business.",
      +      "enum": [
      +        "connection_business"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "customer",
      +    "related_jobs",
      +    "scope"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly/destructive/openWorld, so the description's added value is the scope disclosure: only authorized customers are returned, and address and note fields are deliberately omitted — important so the agent doesn't expect full records. It does not discuss pagination or errors, but for a single-record read that is minor.

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?

Three short sentences, front-loaded with the field-scope constraint. Mild redundancy between 'Returns one authorized customer' and 'Returns customer, related_jobs, scope', but nothing wasteful enough to hurt.

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?

An output schema exists, so the enumerated return keys are largely a convenience rather than a requirement; the critical missing-schema information (which fields are excluded) is present. An agent has enough to call it correctly and interpret the bounded result.

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 coverage; the schema already explains that customer_id comes from search-customers. The description adds no format or sourcing detail beyond that, so baseline 3 applies.

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 and resource ('Returns one authorized customer') plus the exact field scope ('bounded contact and lifecycle fields; addresses and notes are excluded'), which lets an agent distinguish it from list-style lookups. It stops short of naming a sibling tool, so differentiation is implied rather than explicit.

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

Usage Guidelines3/5

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

'Use to get customer in the connected business' gives a usage context but no when-not conditions and no named alternatives (e.g., search-customers appears only in the schema's parameter description). Guidance is implied rather than stated.

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