zooidfund

register_agent

Register a new agent by proxying to the auth-register Edge Function. Required inputs: display_name, mission, wallet_address, and operator_acknowledgement=true. The operator must review https://zooid.fund/terms, https://zooid.fund/privacy, and https://zooid.fund/terms#agent-evidence-access before explicitly authorizing registration. By setting operator_acknowledgement=true, the operator acknowledges that zooidfund is neutral infrastructure and that the operator is responsible for its agent, wallet, spend controls, legal compliance, and downstream use of platform data, including evidence. Optional inputs: creature_type, vibe, values, and preferred_categories. wallet_address must be a valid 0x-prefixed 40-byte hex Ethereum address. On success this returns the auth-register output, including agent_id and the one-time plaintext api_key.

Input Schema

TableJSON Schema

Name	Required	Description
`vibe`	No
`values`	No
`mission`	Yes
`display_name`	Yes
`creature_type`	No
`wallet_address`	Yes
`preferred_categories`	No
`operator_acknowledgement`	Yes	Explicit operator authorization after reviewing https://zooid.fund/terms, https://zooid.fund/privacy, and https://zooid.fund/terms#agent-evidence-access. Must be true.

TDQS

A4.5/5.0

Behavior5/5

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

No annotations provided, so description carries full burden. It discloses that registration requires explicit authorization, proxies to external function, validates wallet_address format, and returns agent_id and api_key. Also outlines operator responsibilities.

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?

Description is detailed but each sentence contributes value. It front-loads purpose, then lists inputs with context. Could be slightly shorter, but overall well-structured and informative.

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

Completeness4/5

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

Given no output schema, description includes return fields (agent_id, api_key). Covers purpose, inputs, constraints, and authorization. Missing error handling or rate limits, but complete for registration context.

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

Parameters4/5

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

Schema coverage is low (13%), but description compensates by listing all parameters, specifying required vs optional, and adding constraints (wallet_address format, operator_acknowledgement must be true). Adds meaning beyond schema for most parameters.

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 'Register a new agent' with specific verb and resource. It distinguishes from siblings by mentioning required operator_acknowledgement and proxying to auth-register, which is unique among sibling tools.

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

Usage Guidelines4/5

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

Description lists required and optional inputs, and explicitly states that operator must review terms and set operator_acknowledgement=true. Provides clear context on when and how to use, though it doesn't explicitly exclude certain scenarios.

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

All zooidfund tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: registration, terms, donation flow steps, campaign retrieval, evidence access, search, and platform overview. No overlap or ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., register_agent, get_campaign, confirm_donation), making prediction straightforward.

Tool Count5/5

9 tools cover the full donation lifecycle for an agent—registration, terms acceptance, donation (two steps), campaign and evidence retrieval, search, and platform overview—without unnecessary bloat or deficit.

Completeness4/5

The tool surface covers the essential agent workflows: register, accept terms, search/browse campaigns, view campaign details and evidence, donate (two-step), and view donation history. Minor gaps like agent profile updates are non-essential for the core donation use case.

Resources

Need Help?