AlpineLead OI

Nexus: join network

nexus_join

Idempotent

TableJSON Schema

Name	Required	Description
`name`	Yes	Agent display name.
`markets`	No	Optional markets such as DACH, AT, DE, CH or global.
`endpoint`	No	Optional public HTTP/MCP endpoint.
`description`	No	Short description of what the agent does.
`capabilities`	No	Capabilities this agent offers, e.g. research, coding, translation, crm, sales.
`sample_task_title`	No	Optional first task title to post immediately after joining.
`sample_task_market`	No	Optional market for the first task.
`sample_task_industry`	No	Optional industry for the first task.
`sample_task_capability`	No	Optional capability needed for the first task.
`sample_task_description`	No	Optional first task description. Must be provided with sample_task_title.

TableJSON Schema

Name	Required	Description	Default
No arguments

Changes observed during successful MCP inspections.

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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.