Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mercari_master

Fetch Mercari's complete reference taxonomy—categories, brands, and sizes—in one call to power filters and lookups. Cache the static results instead of polling.

Instructions

Get Mercari full taxonomy (categories, brands, sizes). Returns Mercari's full reference taxonomy in one call: every category (with parent linkage), every recognized brand, and every clothing/shoe/apparel size. Large (tens of thousands of brand entries) and effectively static -- cache this response rather than polling it.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses payload magnitude ('tens of thousands of brand entries'), stability ('effectively static'), and the operational recommendation to cache instead of poll — a trait that materially affects agent behavior. It omits auth/rate-limit notes, but the size and caching disclosure are the salient behavioral facts for a bulk-read tool.

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?

Three sentences, all front-loaded: identity of the resource first, response contents second, size-and-caching caveat last. No sentence restates the name or wastes tokens; the parenthetical and the em-dash clause each add distinct information.

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

Completeness5/5

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

No output schema exists, yet the description enumerates the returned collections and their key relationships (parent linkage) plus the scale and mutability of the data. For a parameterless reference endpoint that is everything an agent needs to call it and to decide whether to cache the result.

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?

Zero parameters, so per the rubric the baseline is 4; there is nothing for a caller to supply and the description correctly spends no space on parameter syntax. It instead characterizes the response shape, which is the useful analog here.

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?

Specific verb+resource ('Get Mercari full taxonomy') immediately narrowed by a parenthetical enumerating the three content types (categories, brands, sizes). The second sentence expands each with meaningful qualifiers ('with parent linkage', 'recognized brand', 'clothing/shoe/apparel size'), so an agent can distinguish this reference-data tool from transactional siblings like mercari_item or mercari_search.

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

Usage Guidelines4/5

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

The description frames the tool as a bulk reference fetch ('in one call') and explicitly advises caching rather than polling, which is real usage guidance about invocation frequency. It stops short of naming an alternative sibling or stating a when-not condition, but the reference-vs-lookup distinction is clear from the content enumeration.

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

Deploy Server

Other Tools