Skip to main content
Glama

Niche of One Network

Products

find_products
Read-onlyIdempotent

Search existing NoO Network product listings by plain query terms.

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": {
      "query": "<query>"
    },
    "name": "find_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoniche-of-one
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare read-only, idempotent, closed-world, and non-destructive behavior, so the description carries less burden. It adds only that results are 'existing' listings and that search takes plain query terms. It says nothing about how the site-scoping parameter affects results, what happens when limit is omitted, or what a result set looks like.

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 definition is a single clean sentence with no wasted wording. However, the terseness leaves clear gaps, and no structure is used to surface the important scoping and limit constraints.

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?

Annotations cover the safety profile and there is no output schema to explain, which reduces the remaining burden. Even so, a search tool with a scoped site enum and a low limit maximum should tell the agent how scoping and limits work. The description leaves that entirely to the schema.

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 compensate for three parameters. It only hints at query semantics with 'plain query terms' and never mentions the site enum with its 'niche-of-one' default or the limit cap of 5. The two most consequential parameters are left unexplained.

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 states a specific verb and resource: 'Search existing NoO Network product listings by plain query terms.' An agent can tell this is a product search operation. It does not differentiate itself from siblings like mall_browse or mall_product, so it stops short of a 5.

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 guidance on when to use this search instead of mall_browse, mall_product, or mall_reviews. The only usage signal is the phrase 'plain query terms', which describes input style rather than when-to-use conditions or exclusions.

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