Skip to main content
Glama
Sign In
Stables MCP Server

Stables MCP Server

Official
by stables-money
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update customer metadata

update_customer_metadata
DestructiveIdempotent

Update customer metadata key-value pairs to manage specific attributes for stablecoin transactions. Modify customer profiles by setting or changing required data points via the Stables API.

Instructions

Update customer metadata key-value pairs

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": {
      "customerId": "<customerId>",
      "metadata": "<metadata>"
    },
    "name": "update_customer_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
metadataYesMetadata key-value pairs to set
customerIdYesThe customer ID to update metadata for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.6.11
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / metadata / propertyNames
      Added value: +{
+  "type": "string"
+}
  2. First observedv1.4.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds nothing to explain what that destruction means. The critical unanswered question — whether the supplied object merges into existing metadata or replaces it wholesale — is left entirely implicit, which is a serious gap for a tool flagged destructive.

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?

A single short phrase with no wasted words, but the brevity is under-specification rather than efficiency. There is no front-loaded statement of effect or scope to anchor the agent.

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

Completeness2/5

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

For a destructive mutation that takes a nested object, the description should at minimum clarify merge-versus-replace semantics and whether removed keys are deleted. With no output schema and no annotations explaining the mutation's blast radius, the description leaves an agent unable to call this safely.

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% and both parameters are documented inline, so the schema carries the load. The description's only contribution ('key-value pairs') duplicates the schema's own wording for the metadata object and adds no constraint or format detail.

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

Purpose2/5

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

The description is essentially a restatement of the title and tool name, adding only the phrase 'key-value pairs.' It does not say what kind of metadata, what effect the update has, or how it differs from the sibling update_customer.

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 update_customer, create_customer, or any other sibling. There are no stated prerequisites, and no exclusions or conditions are mentioned.

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