Skip to main content
Glama

Customer (order to cash)

o2c_get_customer
Read-onlyIdempotent

Customer with live credit position: limit, open AR, committed value, available.

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": "o2c_get_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
customer_idYesThe customer. An existing customer id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds one genuinely useful behavioral fact: the credit position is 'live' (computed at call time rather than a stored snapshot). It says nothing about freshness guarantees, aggregation window, or behavior for a customer id that doesn't exist.

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?

One compact sentence with zero filler, and the differentiating detail (live credit position) is front-loaded. It is borderline under-specified rather than verbose, so conciseness itself is not the problem.

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?

For a single-parameter read tool with no output schema, enumerating the returned fields is a reasonable partial substitute. But it leaves the agent unable to decide between this and sibling customer/AR readers, and gives no hint about what the 'available' figure is net of, which matters for credit decisions.

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 coverage is 100% for the single customer_id parameter, so the schema already carries the semantics. The description adds nothing about id format, cross-workspace scope, or whether the id must be an existing CRM/bridge customer — baseline 3 applies.

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

Purpose3/5

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

The description names the resource and enumerates what comes back (credit limit, open AR, committed value, available), which implies a read of a customer's credit position. However it is a noun fragment with no verb and it does not distinguish this from o2c_customer_statement or core_get_customer, both of which an agent could plausibly pick for the same intent.

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?

There is no when-to-use guidance at all. With siblings like o2c_customer_statement (statement), o2c_ar_aging (aging), and core_get_customer (core record) in the namespace, the agent gets no signal about which one to call for credit exposure versus invoice history.

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.