get_onboarding_linkGenerate a link for a new member to join NCTR Alliance. Optionally include a referral code. Returns the sign-up URL and a summary of what new members earn.
| Name | Required | Description | Default |
|---|---|---|---|
| referral_code | No | Optional referral code to credit the referring member |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden of disclosing behavior. It states that the tool generates a link and returns a sign-up URL plus earnings summary, but it does not mention any side effects, permissions, or whether the operation is persistent. It adds some return-value context but lacks deeper behavioral transparency.
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?
The description is two sentences, front-loaded with the core purpose, and contains no redundant information. Every word contributes to understanding the tool's function and return value.
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?
For a simple tool with one optional parameter and no output schema, the description covers the key elements: what it generates, the optional parameter, and what it returns. It is slightly incomplete in not addressing potential caveats like link expiration or authentication, but it is adequate for the tool's simplicity.
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 coverage is 100% for the single parameter referral_code, and the schema description already explains its purpose. The description restates that the code is optional and credits the referring member without adding meaningful new information beyond the schema.
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?
The description clearly states the tool generates a link for a new member to join NCTR Alliance, with an optional referral code. This is a specific verb+resource combination that distinguishes it from sibling tools focused on requirements, promotions, rates, funding, and bounties.
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?
The description implies the tool is for creating onboarding links, but it does not explicitly state when to use it over alternatives or provide exclusions. No mention of when not to use it or comparisons to other 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 aspect of the NCTR ecosystem: tier requirements, promotions, earning rates, funding, communities, onboarding, and bounties. The only potential overlap is between tier requirements and earning rates, but descriptions clearly separate requirements from multipliers. No ambiguity exists in selecting the appropriate tool for a task.
All tool names follow a consistent verb_noun pattern, with six using 'get_' and two using 'check_' and 'search_' respectively, all adhering to a verb-first convention. The naming is uniform and predictable across the entire set.
With 7 tools, the server is well-scoped for covering the NCTR program's informational and onboarding capabilities. Each tool serves a unique purpose without redundancy, and the count falls comfortably within the ideal 3-15 range.
The server covers major informational needs: tier progression, earning rates, bounties, promotions, funding, and impact engines. It lacks a direct 'get my status' or 'get my referral code' tool, but for a public-facing informational server, these are minor gaps that agents can work around.