Skip to main content
Glama

Vitrine: Trending Fashion, Luxury, Sneakers & Design

Filter vocabulary

vocabulary
Read-onlyIdempotent

The exact controlled values agents should use in filters and taste profiles, read from the live catalog with item counts: categories, catalog tiers, price tiers with their price bands, availability, trend statuses with meanings, style tags, silhouettes, occasions, seasons, colors, materials, sizes, conditions and ship-to regions, plus every filter field name with its type. No arguments. Cacheable: call it once per session, before building filters.

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

Input Schema

NameRequiredDescriptionDefault
agentNo

Output Schema

NameRequiredDescriptionDefault
metaYes
valuesYes
filtersYes
items_indexedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description goes beyond them by disclosing that values are 'read from the live catalog with item counts' (freshness and richness of the payload) and that the result is cacheable for the session — real behavioral context. It stops short of describing payload shape or size, but an output schema exists to carry that.

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?

Purpose and the caching instruction bracket the description, so it is front-loaded and closes with the actionable rule. The long enumeration of vocabularies earns most of its length by telling the agent what it will receive, though it could be trimmed slightly without losing meaning.

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?

For a zero-required-argument lookup with a full output schema and complete annotations, the description covers what it returns, why to call it, and caching strategy — enough to invoke it correctly. The only omission is any mention of the optional agent identification block, which is minor given the tool works without it.

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 reported at 0%, so the description would normally need to compensate for the single optional 'agent' parameter. It instead says 'No arguments', which is functionally true for required inputs but never mentions the optional self-identification object, whose purpose (better ranking) lives only in the schema. Adequate to drive a correct zero-argument call, but it does not add meaning beyond the schema.

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?

States a specific resource and payload: 'the exact controlled values agents should use in filters and taste profiles', then enumerates the vocabularies (categories, price tiers with bands, trend statuses with meanings, sizes, conditions, ship-to regions) plus 'every filter field name with its type'. This clearly separates it from siblings like search or trending, which consume these values rather than define them.

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

Usage Guidelines5/5

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

Gives explicit when-to-use and how-often: 'call it once per session, before building filters', and explicitly excludes the need for inputs with 'No arguments'. An agent knows both the trigger point and the call cadence without inference.

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