Skip to main content
Glama

Niche of One Network

Browse the site

site_browse
Read-onlyIdempotent

Open any public page of nicheof.one by its path ("/", "/academy/", "/shop/first-frequency/"): its text, the site navigation, the pages under it and what a visitor can do there. Long pages come in parts. Long text: best shown to the user as a document or artifact.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPart of a long page, and page of its child list.
pathNoAn absolute site path, like /academy/. Defaults to the home page.
childrenNo

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 cover read-only, idempotent, closed-world, non-destructive behavior. The description goes beyond them by disclosing what is returned (page text, navigation, child pages, available visitor actions), that long pages are split into parts, and a presentation recommendation to surface long text as a document or artifact.

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?

Compact and mostly front-loaded: what the tool opens, what it returns, then pagination and presentation tips. The parenthetical path examples and the artifact tip both earn their place, though the sentence fragments ('Long pages come in parts.') read clipped rather than polished.

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?

With no output schema, the description does a fair job of sketching the return payload and pagination. It remains incomplete on the children toggle and on the interaction between page-part numbering and the child list bounds, which matter for a 3-parameter paging tool.

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?

With 67% schema coverage, the description usefully clarifies path format via examples and hints that the page parameter relates to parts of long pages ('Long pages come in parts'). However, the children enum (all|none) is left unexplained in both schema and description, so a third of the parameters gain no added meaning.

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: open any public page of nicheof.one by its path, with three concrete path examples and an enumeration of what comes back (text, navigation, child pages, visitor affordances). It does not explicitly distinguish itself from section-specific siblings like academy_browse or mall_browse, so the agent must infer that this is the general-purpose reader.

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: 'Open any public page ... by its path' tells the agent the precondition is having a path, but there is no explicit when-to-use/when-not and no named alternative for the case where the agent lacks a path (e.g. search_site) or wants a section-specific browser.

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