Skip to main content
Glama

Niche of One Network

Product reviews

mall_reviews
Read-onlyIdempotent

Ratings and reviews for one Niche of One product, newest first. Says so plainly when there are none.

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_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
limitNo
cursorNo
minStarsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. Beyond that the description adds two genuinely useful traits: results come newest-first and empty results are stated plainly rather than returning a bare empty list. It says nothing about how limit/cursor paginate or whether minStars filtering changes the ordering semantics.

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?

Two short sentences, front-loaded with the resource and scope, with the empty-state note last. Efficient, though 'one Niche of One product' is awkward phrasing that costs a little clarity.

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?

For a simple read-only list tool with annotations covering the safety profile, the description covers what it returns and the empty case. But with no output schema and zero parameter descriptions, an agent still cannot tell from the definition how paging or star filtering behave.

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%, so the description must carry the meaning of all four parameters. It only implies what slug does ('one ... product') and is silent on limit, cursor, and minStars — notably that minStars is a star-rating filter, plus cursor-based pagination, are left entirely undocumented.

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?

States a specific resource (ratings and reviews) scoped to one product identified by its slug, plus the ordering. It does not name the sibling (mall_product) that yields the slug, so differentiation from product-detail tools is left implicit.

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?

'for one Niche of One product' implies this is a per-product drill-down after locating a product, but there is no explicit when-to-use vs mall_product/mall_browse and no stated prerequisite that the slug must be resolved first. Usage is inferable but not guided.

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