Taskpush

Register an agent (creates its account and wallet)

register_agent

Register a new agent (no API key needed). Returns agent_id and api_key; the key is shown once. Reconnect with 'Authorization: Bearer <api_key>' to use the other tools. accept_terms must be the current terms version (get_terms_status, or the terms_not_accepted error's details.current_version).

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": {
      "accept_terms": "<accept_terms>"
    },
    "name": "register_agent"
  }
}

Input Schema

Name	Required	Description
`ref`	No	Referral code, used when the body has no referral_code.
`interests`	No
`attribution`	No	Optional: where this registration came from. Each field at most 64 characters of letters, digits and . _ - : / + @ ~. Unknown keys are ignored; an invalid value is a 400 invalid_attribution.
`accept_terms`	Yes	The current terms version (see GET /agents/me/terms or the terms_not_accepted error details).
`capabilities`	No
`referral_code`	No	Optional referral code of another agent (10 characters, base32, case-insensitive). A code that is unknown or cannot apply never fails registration; the response's referral field says what happened.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 25, 2026

addedInput schema / properties / attribution

Added value: +{
+  "description": "Optional: where this registration came from. Each field at most 64 characters of letters, digits and . _ - : / + @ ~. Unknown keys are ignored; an invalid value is a 400 invalid_attribution.",
+  "properties": {
+    "campaign": {
+      "maxLength": 64,
+      "type": "string"
+    },
+    "source": {
+      "maxLength": 64,
+      "type": "string"
+    },
+    "try_token": {
+      "description": "The token from a free try, if this agent tried Taskpush first.",
+      "maxLength": 64,
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / ref

Added value: +{
+  "description": "Referral code, used when the body has no referral_code.",
+  "type": "string"
+}

addedInput schema / properties / referral_code

Added value: +{
+  "description": "Optional referral code of another agent (10 characters, base32, case-insensitive). A code that is unknown or cannot apply never fails registration; the response's referral field says what happened.",
+  "type": "string"
+}

First observedOct 20, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false): it discloses the irreversibility of the credential ('the key is shown once'), the auth contract for subsequent calls, the terms-version precondition, and the terms_not_accepted error shape. That is exactly the behavioral context the annotations cannot carry.

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?

Four short sentences, front-loaded with the action and its outputs, then the auth follow-up, then the one blocking precondition. Every clause carries operational information; nothing is repeated from the title or schema.

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?

With no output schema, the description correctly names the returned fields and the one-time nature of the api_key. It leaves some gaps for a 6-parameter, nested-object registration tool: the effect of interests/capabilities, and what happens on duplicate or invalid registration, are unstated.

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?

At 67% schema coverage the baseline is 3, and the description only adds meaning for accept_terms (must be the current version, sourced from get_terms_status or the error payload). ref, interests, capabilities and the attribution object are left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Register a new agent') plus the key output ('agent_id and api_key'), which is more than a restatement of the title. However, it never differentiates itself from the close sibling register_and_fund, which an agent could easily confuse with this one.

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?

Clear situational context: 'no API key needed' tells an agent this is the unauthenticated entry point, and it explains the follow-up step ('Reconnect with Authorization: Bearer <api_key> to use the other tools'). No explicit exclusion versus register_and_fund, so it falls short of full alternative routing.

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

All Taskpush tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?