Skip to main content
Glama
respanai

Respan MCP Server

Official
by respanai

get_customer_detail

Retrieve a customer's profile and budget details using their unique identifier, including spending, budget limits, access rights, and environment.

Instructions

Retrieve detailed information about a specific customer including budget usage.

Returns customer profile and budget data:

IDENTIFICATION:

  • id: Internal customer ID

  • customer_identifier: Your unique identifier for this customer

  • email: Customer email (if provided)

  • name: Customer name (if provided)

  • environment: Environment (prod/test)

  • organization_name: Owning organization name

BUDGET & SPENDING:

  • period_budget: Budget limit for current period (USD, null if unlimited)

  • budget_duration: Budget period type (e.g., "monthly")

  • total_period_usage: Spending in current period (USD)

  • period_start: Current budget period start

  • period_end: Current budget period end (null if ongoing)

  • total_budget: Lifetime budget limit (null if unlimited)

OTHER:

  • has_write_access: Whether customer has write access

  • updated_at: Last update timestamp

NOTE: For usage metrics (requests, tokens, cost, latency), use get_spans_summary with a customer_identifier filter instead.

Use list_customers first to find customer_identifier, then use this for full details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
environmentNoEnvironment: 'prod' or 'test' (default: 'prod')
customer_identifierYesUnique identifier of the customer (from list_customers)
Behavior4/5

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

No annotations provided, so the description carries the burden. It thoroughly explains the return fields, including null/ongoing semantics ('null if unlimited', 'null if ongoing'). It does not explicitly state read-only behavior or error conditions, but the level of detail exceeds typical descriptions and follows the pattern of a safe GET operation.

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 long but extremely well-structured with clear sections (IDENTIFICATION, BUDGET & SPENDING, OTHER) and a leading summary sentence. Every bullet adds necessary detail, and the NOTE section provides crucial cross-tool guidance without fluff.

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?

Given the simplicity of a two-parameter GET tool and the lack of an output schema, the description fully compensates by enumerating all response fields with types/meanings. It also disambiguates from get_spans_summary, making it clear what data is and isn't returned. Minimal gaps exist.

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 coverage is 100%, so parameters are already documented. The description adds value by telling the user to obtain customer_identifier from list_customers, which clarifies the parameter's origin and usage. Environment is self-explanatory via schema enum.

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?

'Retrieve detailed information about a specific customer including budget usage' is a specific verb+resource statement. The description further distinguishes from sibling tools by noting 'use get_spans_summary' for usage metrics and 'Use list_customers first' to find the identifier, clarifying scope.

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

Usage Guidelines5/5

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

Explicitly names alternatives: 'NOTE: For usage metrics... use get_spans_summary' and provides a workflow: 'Use list_customers first to find customer_identifier, then use this for full details.' Clear when-to-use and when-not-to-use guidance.

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/respanai/respan-mcp'

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