Skip to main content
Glama

Register a Humanity Loop contributor node

contributor_register

Create a pseudonymous Humanity Loop contributor node. If risk_permissions is omitted, only Tier-0 reversible work is authorized. Tier-1 requires explicit opt-in and is outside the current Stage-0 pilot; Tier-2 requires explicit human approval. Returns a private node token shown once.

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

Input Schema

NameRequiredDescriptionDefault
hostNo
emailNo
languagesNo
capabilitiesNo
risk_permissionsNo
user_agent_labelNo
allow_tier1_reviewNo
setup_email_consentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / risk_permissions
      Added value: +{
      +  "items": {
      +    "enum": [
      +      "tier0",
      +      "tier1-auto",
      +      "tier2-review"
      +    ],
      +    "type": "string"
      +  },
      +  "maxItems": 3,
      +  "type": "array"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the default authorization scope when risk_permissions is omitted (Tier-0 reversible only), the approval requirements for Tier-1/Tier-2, and the critical fact that the returned node token is shown only once. It omits auth requirements, duplicate/email idempotency behavior, and any rate limits.

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

Conciseness4/5

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

Four short sentences, front-loaded with the purpose, followed by the conditional default, the tier constraints, and the return value. Every sentence carries information; the Stage-0 pilot aside is slightly tangential but contextualizes the Tier-1 restriction.

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?

For an 8-parameter registration tool with no annotations and no output schema, the description covers purpose, tier gating, and the one-time token return. It does not cover what the remaining parameters do, whether registration is idempotent for a repeated email, or what the node token is subsequently used for.

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

Parameters2/5

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

Schema description coverage is 0% across 8 parameters, so the description must compensate and largely does not. It explains the tier enum semantics and default for risk_permissions well, but host, email, languages, capabilities, user_agent_label, allow_tier1_review, and setup_email_consent are left entirely undocumented, including the consent boolean which has privacy implications.

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

Purpose4/5

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

States a specific verb ('Create') and resource ('pseudonymous Humanity Loop contributor node'), which is unambiguous against siblings like contributor_checkin or contributor_submit. It does not explicitly contrast itself with those siblings, but the create-vs-existing-node distinction is inferable from the verb.

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?

Usage is implied: you call this to obtain a node before other contributor_* operations, and the risk_permissions paragraph implies prerequisites for higher tiers. There is no explicit 'when not to use' statement or named alternative for already-registered contributors.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.