Search verified creator content on Nibgate. Returns content metadata (title, type, price, domain, reputation, unlock path). Use to discover what paid/free content exists.
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Search term across title, description, tags, site name, and domain. | |
| skip | No | Pagination offset. | |
| sort | No | Sort order. Defaults to trending. | |
| type | No | Content type filter. | |
| limit | No | Max results (default 20). |
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.
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.
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.
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.
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.
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.
Add one secure layer between your agents and this server.
Each tool targets a distinct concern: content discovery, rankings, ledger activity, platform totals, and Nibshare resolution. There is no meaningful overlap between them, and the descriptions make the boundaries clear.
All tool names follow a consistent verb_noun pattern: explore_content, get_leaderboards, get_ledger, get_platform_stats, resolve_share. The naming is uniform and predictable.
Five tools is a well-scoped set for a public data/read-only platform server. Each tool serves a clear purpose without redundancy or bloat.
The toolkit covers core read-only needs: finding content, viewing rankings, checking ledger activity, seeing platform totals, and resolving share links. A direct content or creator detail endpoint is missing, but the existing tools cover the main discovery and analytics workflows.