Skip to main content
Glama

Collection summary

my_collection_summary
Read-onlyIdempotent

Your SlabLineage collection in numbers: item count, total value at SL Consensus prices (condition-adjusted, times quantity), cost basis, and the change over a range, matching the app.

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": "my_collection_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeNoRange for the change (default 24h).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds genuine value by disclosing the valuation methodology (SL Consensus prices, condition-adjusted, multiplied by quantity) and that results match the app. It does not cover caching, cost-basis calculation basis, or staleness of prices, so it adds context without being rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence, front-loaded with the subject and immediately followed by the returned metrics; nothing is filler. It is somewhat dense with parenthetical detail, but every clause (condition adjustment, quantity multiplication, app parity) carries information an agent would otherwise lack.

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 takes on the burden of describing return values, and it does so by enumerating the four metric groups. Combined with the enum range parameter and full safety annotations, an agent has enough to call this correctly and interpret the result, though the units/currency of 'total value' and 'cost basis' are unstated.

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 coverage is 100% and the enum values plus the 24h default are documented in the schema itself. The description restates that the range applies to 'the change' but adds no format or interpretation guidance beyond the schema. Baseline 3 applies.

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?

Names the resource ('Your SlabLineage collection') and enumerates the specific metrics returned: item count, total value, cost basis, and range change. It is clearly an aggregate-summary tool, distinguishable in kind from sibling actions like record_purchase or search_my_collection, though it never explicitly contrasts itself with a sibling such as collection_movers.

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?

Usage is only implied: an agent can infer this is the tool for a high-level portfolio overview, and the 'range' parameter hints at trend inspection. There is no explicit when-to-use statement, no when-not-to-use, and no named alternative for time-series or per-card breakdowns.

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