Skip to main content
Glama

Niche of One Network

Buy

buy
Read-onlyIdempotent

Return a checkout link for one product in the Niche of One store that NoO Network sells through. Pass a product slug or title. A clear match returns its title, price, checkout link and product page; an unclear one returns up to three candidate products with no link. This tool never takes payment itself: the person opens the link and pays on our Stripe checkout page, and the product is delivered to their email. It does not sell plans or memberships.

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": {
      "product": "<product>"
    },
    "name": "buy"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoniche-of-one
productYesProduct slug, or its title in plain words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Adds real behavior beyond the readOnly/idempotent annotations: it never takes payment, the person pays on an external Stripe page, delivery is by email, and ambiguous matches return up to three candidates with no link. This resolves the apparent tension between a tool named 'buy' and a readOnly annotation, so no contradiction exists.

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?

Four tight sentences, front-loaded with the action and followed by the return shape, the payment caveat, and the exclusion. Dense but every sentence carries information; the only cost is that the caveat and exclusion share space with the core definition.

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 does the work of explaining both return branches (matched product fields vs. up to three candidates), which is exactly what an agent needs. The remaining gap is the undescribed 'site' parameter, the one thing an agent could get wrong.

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

Parameters3/5

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

Schema coverage is only 50%, and the description explains the 'product' parameter (slug or plain-word title) including its fuzzy-match behavior, which adds meaning beyond the schema. However, the 'site' parameter and its eight-value enum are never addressed; the description says 'the Niche of One store' in the singular, which does not prepare an agent for the multi-site enum.

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?

States a specific verb and resource ('Return a checkout link for one product') plus the store context, and explicitly carves out what it is not ('does not sell plans or memberships'), which routes an agent away from plans_info. An agent can distinguish it from find_products or mall_product without opening a schema.

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?

Gives a clear trigger ('pass a product slug or title') and describes the two outcome branches, so an agent knows how to react to an ambiguous match. It lacks an explicit statement of when to prefer find_products or mall_product for browsing versus buying, which keeps it short of a 5.

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