Skip to main content
Glama

Tally by Outpost

Customer lifetime value

get_customer_value
Read-onlyIdempotent

Lifetime value by the source that first brought each customer: customers, revenue, average per customer, renewals and repeat rate, over every payment on record.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_customer_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoThe site's id. Optional: the API key's site is the one read.
limitNoRows at most (default 50).
filtersNoVisits that match every filter (AND). Each dimension at most once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add semantics — and it does: it discloses that grouping is by FIRST-touch source and that the calculation spans 'every payment on record,' i.e. no implicit date window. It does not mention row ordering, pagination behavior beyond the schema's limit, or what an empty result means, which keeps it from a 5.

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?

A single front-loaded sentence that states the grouping first and then enumerates the metrics, with no filler or restatement of the title. Every clause carries information the schema and annotations do not.

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

Completeness4/5

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

With no output schema, the description must convey return content — and it lists the metrics returned plus the row dimension (acquisition source), which is the essential shape of the response. Remaining gaps (sort order, row identity when source is empty/Direct, how renewals and repeat rate are defined) are minor for a read-only reporting tool whose filters are fully documented in the schema.

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 the nested filters object documents each dimension with examples, so the schema carries the parameter burden and the baseline of 3 applies. The description adds the grouping concept but does not clarify the potentially confusing interaction between the `source` filter (a visit's source) and the first-touch source used for grouping, nor how `limit` orders rows.

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

Purpose4/5

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

The description names the resource (customer lifetime value), the grouping dimension (the source that first brought each customer), and the concrete metrics emitted (customers, revenue, average per customer, renewals, repeat rate). An agent can tell this is an attribution-based LTV report rather than a generic breakdown. It stops short of naming a sibling it is not, so it lands at 4 rather than 5.

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 / when-not guidance and no pointer to alternatives such as get_breakdown, get_purchase_paths, or compare_periods for related analysis. The use case is only implied by the metric list. An agent must infer from the name alone that this is the first-touch LTV tool rather than a filtered revenue query.

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.

Resources