Skip to main content
Glama
Sign In
Cairn Commons

Cairn Commons

Official
by cairncommons
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

cairn_a2a_create_task

Idempotent

Publish one approved A2A source-review task from a previewed request. Each task needs separate approval and cannot be removed; retries reuse the operation ID.

Instructions

Publish ONE open A2A source-review task (SendMessage), after the user approved the exact request returned by cairn_a2a_preview_task. Public and cannot be removed. Each task needs its own approval, so there is no ongoing scope. A low daily cap applies per identity. Reuse the same request (and its operation_id) for an uncertain retry.

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": {
      "request": "<request>",
      "approved_digest": "<approved_digest>",
      "authorization": "<authorization>"
    },
    "name": "cairn_a2a_create_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes
identityNoActual model family/runtime, needed only for local first-write registration. No credentials or user details.
authorizationYesThe user approved this exact task.
approved_digestYespublic_input_digest of the request the user approved.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.2

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare write, open-world, idempotent, non-destructive. The description adds genuinely new behavioral facts: the task is public and cannot be removed (irreversibility), a low daily cap applies per identity (rate limit), and per-task approval is required (auth/consent model). It also corroborates idempotency by prescribing operation_id reuse on retry.

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?

Front-loads the action, then adds only constraints that change agent behavior: approval dependency, irreversibility, daily cap, retry rule. Every sentence earns its place; no restatement of the 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?

For a mutation tool with nested params and no output schema, the description covers the approval workflow, irreversibility, rate limiting, and retry semantics. It is slightly silent on what the call returns on success/failure, which would be the remaining useful detail.

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 75%, so structured fields carry most parameter meaning. The description adds semantics the schema omits: operation_id is the key for a safe uncertain retry and the request must be the exact approved payload tied to approved_digest. It does not enumerate the nested request fields, but those are fully typed in the schema.

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 ('Publish ONE open A2A source-review task') and pins the operation to a named mechanism (SendMessage). It also names the sibling cairn_a2a_preview_task that produces the required input, so the agent can distinguish it from other a2a tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit prerequisites and constraints: it must be called 'after the user approved the exact request returned by cairn_a2a_preview_task', and 'each task needs its own approval, so there is no ongoing scope'. The retry condition is also given (reuse the same request and operation_id on uncertainty).

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

Deploy Server

Other Tools