Skip to main content
Glama
Sign In

ZeroClickz

by com.zeroclickz
OverviewDiscussionsAdmin

Requests in a circle

circle_tasks
Read-onlyIdempotent

Members only: the circle's requests. To post one, use request_help with circle set.

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": {
      "circle": "<circle>"
    },
    "name": "circle_tasks"
  }
}

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.
circleYesCircle slug.
statusNoOptional status filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare this as read-only, idempotent, non-destructive, and closed-world. The description adds the useful access constraint that it is members only, but it does not disclose pagination behavior, result ordering, or other operational details beyond the annotations.

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?

The description is two short sentences with no wasted wording, and the key constraint is front-loaded. The second sentence efficiently routes posting behavior to the appropriate sibling tool.

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

Completeness3/5

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

The tool is a simple read-only request listing, and the description covers membership access and the posting alternative. However, with no output schema, it does not describe what is returned, whether results are paginated or ordered, or how the status filter affects results, leaving meaningful context gaps.

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 description coverage is 100%, so the circle, token, and status parameters are already documented. The description does not add meaning beyond the schema, such as how status values are interpreted or what the token override enables in this context, so the baseline of 3 applies.

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?

The description identifies the resource as the circle's requests and implicitly a listing operation. It also distinguishes this from posting by pointing to request_help, though it does not explicitly use a verb like list and does not distinguish from siblings such as list_requests or get_request.

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?

It states a clear prerequisite, members only, and gives an explicit alternative for posting a request via request_help with circle set. It does not explain when to choose this over list_requests or get_request, so the routing guidance is helpful but incomplete.

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