Tool registration turns an external capability into a managed platform resource. A registration records the tool schema, model-facing documentation, execution endpoint, credential reference, and behavioral metadata so authorized applications can discover and invoke it without rebuilding the integration. section 6.1.1 section 10.6
A production-oriented registration typically defines:
- A stable name, description, and parameter schema that models can use for tool selection and argument construction. section 10.6 section 6.2.1
- An execution endpoint and a credential_ref pointing to managed credentials rather than embedding secrets in application code. section 10.6 section 6.1.1
- Behavior metadata such as read-only and idempotent status, plus rate limits that inform guardrails and prevent uncontrolled calls. section 10.6
- Capabilities and tags that support discovery by function, namespace, or constraints such as read-only access. section 6.2.1
Registration is the first phase of a broader lifecycle: discovery exposes complete definitions, validation checks arguments before side effects, and execution injects credentials and standardizes external responses. Registering an MCP server extends the same model by importing the tools it exposes. section 6.1.1
Calendar action registration
A calendar tool can register a name such as claw.calendar.create_event, datetime and attendee parameters, an internal calendar endpoint, credential_ref="calendar-service-account", non-read-only and non-idempotent behavior, and a five-requests-per-session limit. The agent can then receive the registered definition through managed discovery instead of holding credentials or integration details. section 10.6
Listing 10.9 Registering Claw's action tools
platform.tools.register(
name="claw.calendar.create_event",
description="Create a calendar event. Use when the user wants to "
"schedule a meeting or block time.",
parameters={
"title": {"type": "string"},
"start_time": {"type": "string", "format": "datetime"},
"end_time": {"type": "string", "format": "datetime"},
"attendees": {
"type": "array",
"items": {"type": "string"},
"description": "Email addresses of attendees"
}
},
endpoint="https://calendar-api.internal/v1/events",
credential_ref="calendar-service-account", #A
behavior={"is_read_only": False, "is_idempotent": False},
rate_limits={"requests_per_session": 5} #B
)
platform.tools.register( #C
name="claw.tickets.create", #C
# same shape as calendar: parameters, endpoint, credential_ref, #C
behavior={"is_read_only": False, "is_idempotent": False} #C
) #C
platform.tools.register_mcp_server( #D
server_url="http://mcp-web-search:8000", #D
namespace="claw.web" #D
) #DShows the registration interface and how schema, endpoint, credential reference, behavior metadata, and rate limits form one declaration. section 10.6
