Skip to main content
Glama

get_customer

Read-only

Get the customer record linked to the current bearer token. A supplied customer ID must match that token.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
customer_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/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 adds genuinely new behavioral context: the result is derived from the bearer token, and passing a mismatched customer_id is a constraint violation rather than a lookup key. It does not state the failure mode on mismatch (error vs. empty), which keeps it from a 5.

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 short sentences, front-loaded with the identity of the returned record and followed immediately by the constraint on the single parameter. No filler, no restatement of the name or title.

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 an output schema and full annotation coverage, the description supplies what annotations cannot: token-derived scoping and the match requirement. The only gap is the explicit consequence of a mismatched ID, which matters to an agent deciding whether to pass the parameter at all.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the parameter, and it does: customer_id is optional and, when present, must equal the token's customer. That explains why a parameter that looks like a lookup key is really a guard. It does not say what type coercion applies to the string/integer union, but the core semantics are supplied.

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?

Names a specific verb and resource ("Get the customer record") and scopes it to "the current bearer token," which distinguishes it from the contact/domain siblings. It stops short of naming which sibling to use instead when the caller actually wants the authenticated user or a contact, so it is clear but not fully differentiated.

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?

Usage is implied rather than stated: the token-scoping sentence tells the agent this returns only the caller's own customer, and that a supplied customer_id acts as an assertion. There is no explicit when-to-use or when-not-to-use guidance, and no named alternative such as get_contact or get_current_user.

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.