Skip to main content
Glama

Niche of One Network

Product

mall_product
Read-onlyIdempotent

Everything on one Niche of One product page: description, price (fixed, pay what you want or free), rating and reviews, bundle contents, the bundles it is in, related products and the checkout link for the person to open. Takes a slug or a title. It never takes payment.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "mall_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive behavior, so the description only needs to add context—and it does: it explicitly says the tool 'never takes payment' and returns a checkout link 'for the person to open,' which tells the agent the purchase step is out of band. What is missing is failure behavior (unknown slug) and any indication of how large the bundled/related payload may be.

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?

The description is a single dense sentence that front-loads the returned payload and closes with the safety caveat, with essentially no filler. It is long but every clause names a distinct returned element, so the length is justified.

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 one parameter, no output schema, and rich annotations, the main job is describing the return payload—which the description does comprehensively, including price variants and bundle relationships. The only completeness gap is the slug-versus-title ambiguity and the absence of not-found behavior.

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 coverage is 0%, so the description must carry the parameter burden—and it introduces a discrepancy: it says the tool 'takes a slug or a title,' but the schema accepts only a single required 'slug' string and explicitly disallows additional properties. No slug format is explained (e.g., the path segment from a product URL), so an agent reading only the description may attempt a title lookup that cannot succeed.

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 gives a specific resource (a Niche of One product page) and enumerates exactly what is returned: description, price modes, rating/reviews, bundle contents, related products, and checkout link. It is clear what the tool fetches. It does not, however, distinguish itself from siblings like mall_reviews or mall_browse, which overlap with the rating/reviews and catalog portions it claims to return.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus mall_reviews (for just reviews) or mall_browse (for listing products), and no guidance on what happens if the product is not found. The only quasi-usage content is 'Takes a slug or a title,' which is invocation detail rather than when-to-use guidance.

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