Skip to main content
Glama

orb

by io.usefulapi

Update customer

orb_update_customer
Destructive

Updates an existing customer's details (reversible). Only provided fields are changed. Orb API: PUT /customers/{customer_id}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew display name.
emailNoNew billing email (must be a valid email).
currencyNoNew ISO-4217 currency code.
metadataNoUser-defined key/value metadata (string→string).
timezoneNoNew IANA timezone.
customer_idYesOrb customer id (required).
payment_providerNoExternal payment/invoicing provider.
payment_provider_idNoNew id in the external payment provider.
external_customer_idNoNew external id.

TDQS

C2.9/5.0
Behavior1/5

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

The description says the update is '(reversible)', which directly contradicts the annotation destructiveHint: true. This is a serious inconsistency, and the description adds no other behavioral context beyond the partial-update note.

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 with no filler. The main behavior, reversibility caveat, partial-update rule, and API endpoint are all included efficiently.

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

Completeness3/5

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

Given the 9-parameter schema, partial-update semantics, and endpoint, the description is reasonably adequate. However, it does not mention what the tool returns, and the reversibility claim conflicts with the destructiveHint annotation, leaving some context unclear.

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 schema already documents all parameters. The description adds the useful semantic that only provided fields are changed, but it does not add per-parameter meaning beyond the schema.

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 clearly states the operation: updating an existing customer's details, with partial-update semantics and the specific API endpoint. It distinguishes from create/get siblings via the word 'existing', but does not explicitly name alternatives or enumerate which details can be changed.

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?

No guidance is given about when to use this tool versus orb_create_customer or orb_get_customer. The word 'existing' implies it is not for creation, but there is no explicit when/when-not or alternative-routing information.

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

All orb toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation5/5

Every tool name clearly specifies a distinct action and resource (e.g., list_subscriptions vs get_subscription). There is no ambiguity between tools as each targets a unique combination of verb and noun.

Naming Consistency5/5

All tool names follow a consistent pattern: 'orb_<verb>_<resource>' in snake_case. This makes them predictable and easy to distinguish.

Tool Count4/5

With 26 tools, the set covers many resources and operations for a billing platform. While slightly above typical range, each tool justifies its existence given the domain complexity.

Completeness3/5

The tool surface provides extensive read capabilities and basic customer CRUD, but lacks create/update/delete for most other resources (e.g., subscriptions, invoices) and missing operations like void or cancel. This creates notable gaps for full lifecycle management.

Resources