Skip to main content
Glama
Crossdeckhq

Prism

Official
by Crossdeckhq
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Get a customer's full picture

get_customer
Read-only

Resolve a customer by any identifier and view their monthly payment, active entitlements, and database read-cost in one consolidated result.

Instructions

Cross-match one customer across every layer Crossdeck joins by identity. Returns what they pay (monthly cents), their active entitlement count, and their database read-cost — in one view. Identify the person by ANY ONE of the identifiers below; they all resolve to the same canonical customer. Use for 'how much does this user pay and what do they cost us?'. If no customer resolves, returns a no-match result, not an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userIdNoYour own user id for this person — the value you pass to identify() in the SDK (e.g. 'user_847').
projectNoThe app to read, as a project id from list_projects (e.g. 'proj_3a8f137bccdd4f'). With a workspace key (cd_wk_) this is required unless you've set a default via use_project; with a single-app key it is ignored.
customerIdNoA Crossdeck customer id ('cdcust_…').
anonymousIdNoA pre-login anonymous/device id captured before the user signed in.
stripeCustomerIdNoStripe customer id ('cus_…').
googlePurchaseTokenNoGoogle Play purchase token for the customer's purchase.
appleOriginalTransactionIdNoApple StoreKit originalTransactionId for the customer's purchase.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed7 schema fields changedv0.3.2
    • changedInput schema / properties / anonymousId / description
      Previous value: -"A pre-login anonymous/device id."New value: +"A pre-login anonymous/device id captured before the user signed in."
    • changedInput schema / properties / appleOriginalTransactionId / description
      Previous value: -"Apple StoreKit originalTransactionId."New value: +"Apple StoreKit originalTransactionId for the customer's purchase."
    • changedInput schema / properties / customerId / description
      Previous value: -"A Crossdeck customer id (cdcust_…)."New value: +"A Crossdeck customer id ('cdcust_…')."
    • changedInput schema / properties / googlePurchaseToken / description
      Previous value: -"Google Play purchase token."New value: +"Google Play purchase token for the customer's purchase."
    • changedInput schema / properties / project / description
      Previous value: -"The app to read (its project id, from list_projects). With a workspace key this is required unless you've set one via use_project; with a single-app key it's ignored."New value: +"The app to read, as a project id from list_projects (e.g. 'proj_3a8f137bccdd4f'). With a workspace key (cd_wk_) this is required unless you've set a default via use_project; with a single-app key it is ignored."
    • changedInput schema / properties / stripeCustomerId / description
      Previous value: -"Stripe customer id (cus_…)."New value: +"Stripe customer id ('cus_…')."
    • changedInput schema / properties / userId / description
      Previous value: -"Your own user id for this person (what you pass to identify())."New value: +"Your own user id for this person — the value you pass to identify() in the SDK (e.g. 'user_847')."
  2. First observedv0.3.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already mark the tool as read-only. The description adds behavioral context: it returns specific fields (monthly cents, entitlement count, read-cost) and explains the no-match handling. This goes beyond the annotations but does not cover permissions or rate limits.

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?

The description is concise (about 120 words) and structured logically: first sentence for purpose, second for outputs, third for parameter usage, fourth for use case, fifth for edge case. No wasted words, front-loaded with key information.

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

Completeness5/5

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

Despite no output schema, the description clearly states what is returned (monthly cents, entitlement count, read-cost). It also covers the no-match case. With 7 optional parameters, the description explains how to use them (any one). This makes the tool's behavior fully comprehensible for an AI agent.

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

Parameters5/5

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

The schema has 7 parameters with individual descriptions, but the description adds crucial semantics: 'Identify the person by ANY ONE of the identifiers below; they all resolve to the same canonical customer.' This clarifies mutual exclusivity and selection logic, which is valuable beyond the schema's per-parameter descriptions.

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

Purpose5/5

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

The description clearly states the tool's purpose: to cross-match a customer across identity layers and return billing and cost data. It specifies the resource (customer) and the verb (cross-match/get), and distinguishes from siblings like get_revenue by offering a combined view.

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

Usage Guidelines4/5

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

The description explicitly says 'Use for how much does this user pay and what do they cost us?' which gives a clear use case. It also mentions that a no-match returns an informational result rather than an error. However, it does not explicitly mention when not to use this tool or reference sibling tools as alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Crossdeckhq/crossdeck-prism'

If you have feedback or need assistance with the MCP directory API, please join our Discord server