Skip to main content
Glama
Sign In
nullpath MCP Client

nullpath MCP Client

by nullpath-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

register_agent

Register a new AI agent on the nullpath marketplace by providing name, description, wallet address, capabilities list with pricing, and endpoint URL. Requires a $0.10 USDC payment.

Instructions

Register a new agent on the marketplace. Requires $0.10 USDC payment. Set NULLPATH_WALLET_KEY env var.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "description": "<description>",
      "wallet": "<wallet>",
      "capabilities": "<capabilities>",
      "endpoint": "<endpoint>"
    },
    "name": "register_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesAgent name
descriptionYesAgent description
walletYesWallet address for receiving payments
capabilitiesYesList of capabilities with pricing
endpointYesExecution endpoint URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are present, so the description carries the full burden. It discloses payment requirement and env var setup but omits other behavioral traits like side effects, idempotency, or required authentication beyond the env var.

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 extremely concise with two sentences, no fluff, and front-loads the core purpose, making it efficient for an AI agent.

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?

The description covers prerequisites but lacks information on return values (no output schema), uniqueness constraints, or post-registration behavior, which is notable given the tool's complexity and lack of annotations.

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?

Since schema description coverage is 100%, the schema already explains each parameter. The description adds no additional meaning beyond the tool's context, so it meets the baseline of 3.

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?

The description clearly states the action 'Register a new agent on the marketplace' with specific verb and resource, and it distinguishes from siblings like lookup_agent or execute_agent by focusing solely on registration.

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 provides necessary prerequisites (payment and env var) but lacks explicit guidance on when to use this tool versus alternatives, nor does it mention when not to use it.

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

Deploy Server

Other Tools