Skip to main content
Glama

Niche of One Network

OneSearch

onesearch
Read-onlyIdempotent

Search the web privately with OneSearch, our own search engine: no tracking, no profile. scope "web" (default) returns web results with matching Niche of One network pages first; scope "network" searches only our eight sites.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
queryYesWhat to search for.
scopeNoweb

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely non-obvious behavior: results are ranked so matching Niche of One network pages appear first in 'web' scope, and 'network' is bounded to eight sites. The privacy claim is marketing-flavored rather than operative, and result format is not described.

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 sentences, front-loaded with the action and followed by the scope semantics. Minor waste in the promotional phrasing ("our own search engine: no tracking, no profile"), but nothing structurally confusing.

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 three-parameter search tool with strong annotation coverage, the description covers scope behavior adequately. It leaves two gaps an agent would care about: what the 'page' parameter does and, with no output schema present, nothing about what a result entry looks like.

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 33%: 'query' is documented but 'scope' and 'page' have no schema descriptions. The description compensates well for 'scope' by defining both enum values and the default, but 'page' (1-5) is never mentioned, so its meaning and interaction with result volume remain unclear.

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 ("Search the web") and names the engine, which is clearly distinct from the archive/site-specific siblings. It also explains the two internal modes ("scope 'web' ... scope 'network' searches only our eight sites"), giving the agent a precise picture of what gets searched. It does not explicitly contrast itself with siblings like search_site or search_archive, 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 Guidelines3/5

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

Gives clear routing between the two scopes, including which is the default and what 'network' restricts to, so usage within the tool is well implied. However, there is no guidance on when to pick this tool over the many sibling search tools (search_site, search_archive, get_page), leaving that choice to inference.

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