Skip to main content
Glama

human_register_provider

Register a service provider's webhook endpoint to receive matched tasks. Set categories, regions, budgets, and concurrent limits for automated dispatch.

Instructions

Register a new webhook provider to receive dispatched tasks.

Any service provider (law firm, VA agency, freelancer, etc.) can register their webhook endpoint to start receiving tasks that match their profile. The system will POST task payloads to the webhook URL, signed with HMAC-SHA256 using the shared secret.

PARAMETERS:

  • name: Human-readable provider name (e.g. "Smith & Associates Law")

  • webhook_url: HTTPS URL where tasks will be POSTed

  • webhook_secret: Shared secret for HMAC-SHA256 webhook signatures (min 32 characters)

  • categories: Task categories this provider handles (errand, photo_video, data_collection, verification, delivery, digital_micro, in_person, custom)

  • task_types: Task types supported (physical, digital, hybrid)

  • regions: Regions served (e.g. ["US", "EU", "*"] where * = global)

  • min_budget_usd: Minimum task budget accepted (USD)

  • max_budget_usd: Maximum task budget accepted (USD)

  • max_concurrent_tasks: Max simultaneous tasks (default 10)

WEBHOOK FORMAT: Tasks are POSTed with headers:

  • x-dispatch-signature: sha256=

  • X-Dispatch-Event: task.new | task.cancel | provider.verify

  • X-Dispatch-TaskId:

Expected response: { "accepted": true, "external_id": "your-id" } or { "accepted": false, "reason": "..." }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesHuman-readable provider name (e.g. 'Smith & Associates Law')
regionsYesRegions served (e.g. ['US', 'EU', '*'] where * = global)
categoriesYesTask categories this provider handles
task_typesYesTask types this provider supports (physical, digital, hybrid)
webhook_urlYesHTTPS URL where tasks will be POSTed
max_budget_usdYesMaximum task budget this provider accepts (USD)
min_budget_usdYesMinimum task budget this provider accepts (USD)
webhook_secretYesShared secret for HMAC-SHA256 webhook signatures (min 32 chars)
max_concurrent_tasksNoMaximum number of tasks this provider can handle concurrently
Behavior4/5

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

With no annotations, the description carries the full burden. It details the webhook format, HMAC-SHA256 signing, and expected response, but does not clarify behavior on duplicate registrations or error cases.

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?

The description is well-structured with sections, front-loaded with purpose, and each sentence adds value. It is comprehensive but not overly verbose.

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 the complexity (9 parameters, 8 required, no output schema), the description covers purpose, webhook interaction, and expected response. It lacks error details but is generally complete.

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?

Schema coverage is 100%, so baseline is 3. The description largely repeats schema parameter descriptions, though it adds webhook format context that indirectly aids understanding of parameters like webhook_url and webhook_secret.

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 states 'Register a new webhook provider to receive dispatched tasks,' which clearly identifies the verb and resource. It distinguishes from sibling tools like human_dispatch_task and human_list_providers.

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?

The description explains that providers register to start receiving tasks that match their profile, but does not explicitly mention when not to use the tool or suggest alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zyntarasystems/human-dispatch-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server