Skip to main content
Glama

Niche of One Network

Browse the Mall

mall_browse
Read-onlyIdempotent

Walk the Niche of One Mall. No arguments: the floor plan (storefronts and departments). With filters: our products with price, rating and product page, or a partner storefront (makers, catalog, newsstand) with its disclosure. Details, reviews and the checkout link: mall_product.

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

Input Schema

NameRequiredDescriptionDefault
qNo
tagNo
kindNo
sortNo
limitNo
priceNo
cursorNo
sectionNo
featuredNo
maxCentsNo
minCentsNo
departmentNo
storefrontNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 open-world, so the safety profile is covered. The description adds value beyond that by describing mode-dependent output: a floor plan structure in the no-argument case versus product records with price, rating and product page URL, or partner storefront data with a disclosure. It omits pagination behavior entirely despite a cursor parameter, which is the notable gap.

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

Conciseness3/5

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

The description is short and front-loads the no-argument behavior before the filtered behavior, which is the right order. However, the telegraphic, flavor-heavy phrasing ('Walk the Niche of One Mall', 'Details, reviews and the checkout link: mall_product.') costs clarity at the same length a plain sentence would take.

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

Completeness2/5

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

This is a broad, open-world browse tool with 13 optional parameters, zero schema descriptions and no output schema, which is the highest-burden case. The description covers the two modes at a high level but says nothing about filtering dimensions, sort options, result limits or cursor paging, leaving the majority of invocation decisions undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 13 parameters, so the description must carry the load and it largely does not. It hints at storefront/department concepts and names three partner storefronts, but never explains q, tag, kind, sort, limit, price, featured, minCents/maxCents, section or cursor. An agent reading only the description would not know how to filter, sort, or page.

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 browse verb over a mall resource and distinguishes two concrete modes: no arguments returns the floor plan (storefronts and departments), arguments return product listings or a partner storefront. It also explicitly separates itself from mall_product, which handles details, reviews and the checkout link. The only shortfall is that the flavor phrasing ('Walk the Niche of One Mall') delays the actual resource statement.

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?

It gives a clear usage rule: call with no arguments for the floor plan, call with filters for listings, and go to mall_product for details/reviews/checkout. That is a real routing decision an agent can act on. It stops short of distinguishing this from other browse siblings (e.g., site_browse, academy_browse, find_products), so it is not a full when-to-use map.

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