Kellian

Root agent bulk-approves pending link consents into protocol DB membership

kellian_approve_link_consents

Bulk-approve staged link consents into protocol DB membership (up to 20 per call). Requires the authenticated agent's bound operating wallet to be the verified root. Pass consents from kellian_list_pending_link_consents (or the membership snapshot returned after agents call kellian_submit_link_consent). No on-chain linkAddress transaction.

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": {
      "consents": "<consents>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "kellian_approve_link_consents"
  }
}

Input Schema

Name	Required	Description	Default
`consents`	Yes	Pending consents to approve in one batch
`idempotencyKey`	Yes	Stable retry key. Reuse only with byte-equivalent tool arguments.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the description's useful additions are the root-authority requirement and the note that no on-chain linkAddress transaction is fired. It does not say whether a batch is atomic or whether partial success is possible, which is a meaningful gap for a bulk mutation.

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, verb and scope front-loaded, then precondition, then input provenance, then the on-chain clarification. Nothing is wasted or redundant.

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?

An output schema exists, so return values need no explanation, and the description covers authority, input source and batch size. The only missing piece an agent would care about is failure semantics for a partially valid batch.

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 schema already explains consents, targetAddress and idempotencyKey. The description adds only the source of the consents and repeats the 20-item cap that maxItems already encodes, so baseline 3 applies.

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?

States a specific verb and resource ('Bulk-approve staged link consents into protocol DB membership') plus the batch cap. It is clearly distinguishable from the sibling that stages consents (kellian_submit_link_consent) and the one that lists them (kellian_list_pending_link_consents).

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?

Explicitly tells the agent where the input comes from — kellian_list_pending_link_consents or the membership snapshot after kellian_submit_link_consent — and states the precondition that the bound wallet must be the verified root. It does not spell out what to do when some consents are not approvable, but the routing context is strong.

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

All Kellian 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?