Skip to main content
Glama

Collection analytics

get_collection_analytics
Read-only

Explain the signed-in person's collection: its current value, cost and profit, the standout coins, how complete each coin series is, how the value changed over time, or what it held day by day in a period. A missing price is reported as missing, never estimated.

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_collection_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoWith view=history: last day, YYYY-MM-DD, not in the future. Omitted = today.
viewNosummary = what the collection is worth now, what was paid and the profit; statistics = the most valuable coin, the biggest gain and loss, the first purchase; completeness = how full every coin series is; growth = how the value changed over time, by purchase dates; history = what the collection actually held and was worth on each day of a period, as recorded day by day.summary
startNoWith view=history: first day, YYYY-MM-DD. Omitted = 89 days before end.
cursorNoWith view=completeness: next_cursor of the previous page, with the same other arguments.
page_sizeNoWith view=completeness: series per page.
series_idNoWith view=completeness: list every coin of this one series with its status, instead of the table of series. The id comes from get_catalog_entity.
max_pointsNoWith view=growth or history: upper bound of points; a longer series is thinned evenly.

Output Schema

NameRequiredDescriptionDefault
dataYes
as_ofYes
warningsYes
request_idYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnly=true, destructive=false and openWorld=false, so safety is covered. The description contributes genuine extra context: the result is scoped to the signed-in person's own collection, and 'A missing price is reported as missing, never estimated' is a substantive data-integrity guarantee an agent would not otherwise know.

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: the object of the operation comes first, then the five modes in the order they appear in the enum, and one short guarantee sentence at the end. No filler, no repetition of schema defaults.

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 7 fully documented parameters, an output schema and safety annotations, the definition covers what an agent needs to select and call the tool. The only soft spot is that pagination/thinning behavior for the completeness, growth and history views is left entirely to the schema rather than being surfaced in the description.

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% and the per-parameter descriptions already explain view semantics, date defaults, page_size bounds and cursor chaining, so the baseline is 3. The description adds a little framing by paraphrasing each analytical view in question-oriented language, which helps an agent map a user question onto a view, but it adds no syntax or format detail beyond the schema.

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 a concrete verb and resource ('Explain the signed-in person's collection') and enumerates the five analytical angles (value/cost/profit, standout coins, series completeness, value over time, day-by-day holdings), which map one-to-one onto the view enum. It implicitly separates itself from the raw-listing sibling get_my_collection by framing everything as derived analysis, but it never names that sibling, so differentiation is left to inference.

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

Usage Guidelines3/5

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

The 'or' enumeration tells the agent which questions each mode answers, but routing detail (which view, which dates, pagination) lives entirely in the schema's enum descriptions, not here. There is no explicit when-to-use-this-instead-of-get_my_collection guidance and no statement of prerequisites or exclusions.

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