Skip to main content
Glama
AIOProductOS

AIOProductOS

Official
by AIOProductOS
OverviewSchemaSourceRelated ServersDiscussions(2)Admin
JavaScript
Remote

Customer 360

get_customer_360
Read-onlyIdempotent

Resolve any customer by id, email, domain, or company name and retrieve a unified record with profile, subscription, MRR, user count, and verbatim feedback.

Instructions

Everything about ONE customer, resolved by id, email, domain, or company name: profile, subscription + MRR, how many users sit under the account, and their verbatim feedback. Read-only; returns the matched account, or an empty result when nothing matches the query. The money + people + voice join on one record — call it before answering anything about a specific account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe account to resolve: an account id, a user's email, a company domain (e.g. 'acme.com'), or a company name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.14
  2. Removedv0.1.12
  3. Changed1 schema field changedv0.1.5
    • changedInput schema / properties / query / description
      Previous value: -"Account id, email, domain, or company name."New value: +"The account to resolve — an account id (exact), a user's email (exact), a company domain like 'acme.com', or a company name (partial match). Pass one value; the strongest match wins."
  4. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

The description discloses key behaviors beyond annotations: it explicitly mentions read-only behavior (consistent with annotations) and adds the empty-result behavior when no match is found. It also reveals the joined data structure (money + people + voice) and the exact fields returned, providing useful behavioral context not available from annotations alone.

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 three well-structured sentences with no fluff. It front-loads the core value proposition ('Everything about ONE customer'), lists specific data points, and ends with a practical usage tip. Every sentence contributes meaningfully.

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?

For a read-only lookup tool with a single parameter and strong annotations, the description is complete. It covers what data is returned, how the query resolves, empty-result behavior, and when to use it. No output schema exists, but the description explicitly lists the fields returned, compensating fully.

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?

The schema covers the single 'query' parameter fully (100% coverage) with a descriptive explanation of accepted formats. The description repeats this information without adding new semantic details. Baseline 3 is appropriate since the schema does the heavy lifting.

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: retrieving everything about ONE customer (profile, subscription, MRR, user count, feedback) resolved by multiple identifiers. It distinguishes itself from sibling tools by emphasizing its aggregate 360-degree view and note to call it before answering account-specific questions.

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 provides explicit usage guidance: 'call it before answering anything about a specific account.' It also clarifies that it resolves by id, email, domain, or company name. It lacks explicit when-not-to-use or alternative tool references, but the context is clear given the unique nature of the tool.

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