Skip to main content
Glama
Sign In

nctr-mcp-server

by io.github.Hoya25
OverviewDiscussionsAdmin

Search Bounties

search_bounties

Search and filter available NCTR bounties. Filter by category (entry, shopping, merch, referral, engagement), minimum/maximum NCTR amount, or keyword. Returns bounty details including name, amount, commitment period, and requirements. Every bounty is committed through 360LOCK for 360 days. Your NCTR stays yours throughout.

Input Schema

NameRequiredDescriptionDefault
keywordNoSearch keyword to match against bounty name, description, or tags
categoryNoFilter by bounty category: entry, shopping, merch, referral, engagement
max_amountNoMaximum NCTR amount
min_amountNoMinimum NCTR amount
repeatable_onlyNoIf true, only return bounties that can be earned multiple times

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Filter by bounty category"New value: +"Filter by bounty category: entry, shopping, merch, referral, engagement"
    • removedInput schema / properties / category / enum
      Removed value: -[
-  "entry",
-  "revenue",
-  "merch",
-  "referral",
-  "engagement"
-]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and adds useful domain context: returned fields, 360LOCK commitment period, and non-custodial NCTR handling. It still omits pagination, result limits, authentication, and rate-limit behavior, so it is not fully transparent.

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?

The description is front-loaded with purpose, then filters, then return values, then commitment context. Every sentence contributes useful information without repetition or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a search tool with no output schema, the description explains the returned bounty details and the 360LOCK commitment context. It is nearly complete for invocation, though it lacks result limits, ordering, and pagination behavior.

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 100%, so the schema already documents all five parameters. The description mentions keyword, category, and amount filters but omits repeatable_only and adds little beyond the schema's own descriptions.

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 and resource: search and filter available NCTR bounties. It names the filterable dimensions and return fields, making the tool's scope unmistakable and distinct from the informational sibling tools.

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?

The description makes clear how to filter bounties, but it does not explicitly state when to use this tool versus alternatives or when not to use it. Usage is implied by the search/filter language rather than guided.

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

All nctr-mcp-server 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