Skip to main content
Glama

Sneaker collection overview

stockroom_overview
Read-only

Returns sneaker collection and wishlist counts, estimated market value of owned pairs, and brand rankings for a quick stockroom status review.

Instructions

Counts for the sneaker collection and wishlist, the estimated market value of owned pairs, and the top brands.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds that the market value is an estimate and applies only to owned pairs, which is useful context, but says nothing about how values are sourced or what happens with an empty collection.

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 that front-loads the collection counts and then the derived metrics. It is slightly list-like and could use a clearer separator, but no sentence is wasted.

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

Completeness3/5

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

There is no output schema, so the description carries the burden of describing return values. It names the metrics but does not say how many 'top brands' are returned, whether they are ranked, or the units/currency of the market value, leaving the response shape partly unspecified.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly avoids inventing filter options.

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 specific resource (sneaker collection and wishlist) and enumerates the outputs: counts, estimated market value of owned pairs, and top brands. That is clearly distinct from the mutation-oriented siblings, though it never explicitly contrasts itself with an alternative such as stockroom_search.

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: the word 'overview' plus read-only annotations suggest a summary call before or instead of listing individual pairs. There is no explicit statement of when to call this versus stockroom_search or the add/mark tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.