Skip to main content
Glama

zooidfund

by fund.zooid

acknowledge_agent_terms

Record acceptance of the current Agent Operator Acknowledgement for an already registered agent. Requires Authorization: Bearer and operator_acknowledgement=true. The operator must first review https://zooid.fund/terms, https://zooid.fund/privacy, and https://zooid.fund/terms#agent-evidence-access. Use this if get_evidence returns operator_acknowledgement_required. Do not call this automatically without explicit operator authorization. This does not perform KYC, verify identity, or recover lost API keys.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operator_acknowledgementYesExplicit 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.7/5.0
Behavior4/5

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

With no annotations, description fully covers prerequisites (auth, operator_acknowledgement=true) and explicitly lists what it does NOT do (KYC, identity verification, key recovery). Could improve by noting success/error behavior.

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?

Compact, well-organized sentences. No wasted words; each sentence adds critical information (action, auth, usage condition, warning, exclusions).

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

Completeness5/5

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

Given simple parameter schema and tool complexity, description covers all essential aspects: purpose, conditions, prerequisites, and limitations. No obvious gaps.

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 100%, but description adds value by explaining the parameter's meaning ('explicit operator authorization') and linking to the required URLs. Justifies the const=true constraint.

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?

Clear verb 'Record acceptance' and specific resource 'current Agent Operator Acknowledgement for an already registered agent'. Distinct from sibling tools that handle donations, campaigns, etc.

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

Usage Guidelines5/5

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

Explicitly states when to use: 'Use this if get_evidence returns operator_acknowledgement_required.' Also warns against automatic invocation, providing clear usage boundaries.

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

All zooidfund toolsInspect
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