Skip to main content
Glama
Sign In

nibgate

by io.github.fortunesayspump
OverviewDiscussionsAdmin

explore_content

Search verified creator content on Nibgate. Returns content metadata (title, type, price, domain, reputation, unlock path). Use to discover what paid/free content exists.

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

Input Schema

NameRequiredDescriptionDefault
qNoSearch term across title, description, tags, site name, and domain.
skipNoPagination offset.
sortNoSort order. Defaults to trending.
typeNoContent type filter.
limitNoMax results (default 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / sort / description
      Previous value: -"Site order; historical rankings are unavailable."New value: +"Sort order. Defaults to trending."
    • changedInput schema / properties / sort / enum
      Previous value: -[
-  "site-order"
-]New value: +[
+  "trending",
+  "best-sellers",
+  "hot-new"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / sort / description
      Previous value: -"Sort order. Defaults to trending."New value: +"Site order; historical rankings are unavailable."
    • changedInput schema / properties / sort / enum
      Previous value: -[
-  "trending",
-  "best-sellers",
-  "hot-new"
-]New value: +[
+  "site-order"
+]
  3. First observed

TDQS

A3.9/5.0
Behavior3/5

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

No annotations exist, so the description carries the transparency burden. It discloses that this is a search operation returning content metadata and even names the unlock path field, implying read-only behavior. However, it does not mention pagination behavior, defaults, authentication needs, or any side effects, leaving some gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tightly written sentences with the core action front-loaded. The metadata field list efficiently conveys return value scope without unnecessary elaboration.

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 partially compensates by listing key returned fields, but it omits the result envelope and pagination details. Since all parameters are optional, the word 'Search' might misleadingly imply q is required. Adequate for a basic discovery tool, but not fully complete.

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 description coverage is 100%, so the baseline of 3 applies. The description's metadata list (e.g., type, price) loosely relates to filters, but it does not add parameter-specific meaning beyond what the schema already provides.

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 ('Search'), resource ('verified creator content on Nibgate'), and returning content metadata fields. This clearly differentiates it from siblings like get_leaderboards and get_platform_stats, which focus on aggregate metrics rather than content discovery.

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?

Provides a clear use case: 'Use to discover what paid/free content exists.' It does not explicitly mention alternatives or exclusion conditions, but the search/discovery purpose is clearly distinct from the statistical and ledger-oriented sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All nibgate toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources