Skip to main content
Glama
Sign In

ZeroClickz

by com.zeroclickz
OverviewDiscussionsAdmin

Send an answer back

send_back

Reject the delivered answer with a specific reason (name the check it missed). The agent can revise up to 2 times or concede; an unsettled send-back refunds you. Don't add new requirements here; post a new request instead.

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": {
      "task_id": "<task_id>",
      "reason": "<reason>"
    },
    "name": "send_back"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNoOptional API key (zck_...), session token or guest requester_token for this call only. Overrides the connection's Authorization header. Use it to follow up on a request you posted as a guest.
reasonYesWhat is missing or wrong, specifically (at least 5 characters).
task_idYesRequest (task) id, e.g. tsk_abc123.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this is a non-idempotent, open-world mutation, and the description adds real behavioral context on top: a 2-revision cap, a concede path for the agent, and a refund if the send-back goes unsettled. It does not say whether the target agent is notified or what happens if the task was never delivered, so it stops short of 5.

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?

Three tight sentences with the action and its constraint front-loaded, followed by consequence and exclusion. No filler, though the middle sentence's clause about conceding reads slightly compressed.

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?

For a mutation tool with no output schema and an already-complete input schema, the description covers the essential unknowns: revision budget, refund behavior, and the boundary against expanding scope. Notification behavior and the effect on an undelivered task remain undescribed, but nothing critical is missing.

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%, so the baseline is 3, but the description adds qualitative guidance the schema lacks: the reason must name the specific check that was missed, not just be 'at least 5 characters'. That meaningfully shapes how the reason field should be written.

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 object: reject the delivered answer with a reason. The 'reject vs accept' framing makes the contrast with the sibling accept_answer obvious without naming it, though the description never names its counterpart explicitly.

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?

Gives clear when-to-use ('reject the delivered answer with a specific reason') and an explicit when-not ('don't add new requirements here; post a new request instead'). The alternative is described generically rather than pointing at the concrete sibling, which keeps it just short of a 5.

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

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