Skip to main content
Glama

Niche of One Network

Recommend

recommend
Read-onlyIdempotent

Recommend up to three things matched to interests the user states, from the Niche of One shop that NoO Network sells through and from affiliate partners. Our own shop products come first, labelled "From the shop" with price and shop link. An affiliate product, labelled "Partner pick" with an affiliate disclosure, appears only when nothing of ours fits or as the third pick. When the client sends a member sign-in, a plan the account already holds is not offered. Interests are matched for this call only and are not stored.

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

Input Schema

NameRequiredDescriptionDefault
siteNoniche-of-one
offersNofalse returns no picks.
interestsNoTopics or interests, in plain words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/closed-world annotations: caps results at three, defines ordering and labeling ('From the shop' with price and link, 'Partner pick' with affiliate disclosure), suppresses already-held plans for signed-in members, and states interests are not persisted. That is exactly the behavior an agent needs to set expectations.

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?

Front-loaded with the core action and result cap, followed by sourcing and labeling rules in a logical order. It is somewhat dense and the affiliate-disclosure detail is verbose, but nearly every sentence carries decision-relevant information.

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 no output schema, the description carries the burden of describing returns and does so (labels, price, shop link, affiliate disclosure, max three). It leaves the no-match/empty case and the role of the site parameter unstated, which is a modest gap for a three-parameter tool.

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?

Schema coverage is 67%, and the description meaningfully explains 'interests' (matched for this call only, not stored) and indirectly frames 'site' as the shop being recommended from. It does not explain the eight-value site enum or clarify when to set offers=false, but the added meaning is real.

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 verb and resource: recommends up to three items matched to stated interests, sourced from the Niche of One shop plus affiliates. It is clearly a curated recommendation tool rather than a product search, though it never names a sibling like find_products or mall_browse to sharpen the boundary.

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?

Usage is implied rather than stated: an agent can infer to call it when a user expresses interests. It explains internal rules (shop products first, affiliate only when nothing fits or as third pick, no offering already-held plans) but gives no explicit when-to-use-this-vs-alternatives 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