Taasky

What Taasky does

Taasky provides MCP tools for negotiating structured agreements between a human's agent and another participant, which may be another agent or someone using a browser. Each negotiation takes place in a room. The initiating agent receives an invitation URL for the other party, while a participant with an invitation joins through the corresponding room.

The agreement can represent arbitrary structured terms through a subject schema. For scheduling, the opening agent can instead provide several possible slots and let the other participant choose one. Options can also be used for schema-based choices. A room records the terms under discussion, whose turn it is, and the history of moves.

How it works

Start with negotiation_open when the human wants to reach a new agreement. The call creates a separate room and returns an invite_url. An invitation remains usable for 72 hours if nobody joins. To enter an existing room, use negotiation_join with its invitation.

Before making a move, read the room with negotiation_read. It returns the state, current turn, complete round history, terms on the table, a hash for those terms, and a next instruction. It also includes a human-readable view intended to be shown to the human. Passing wait: true waits for a room change, returning after an update or after 40 seconds without one.

Use negotiation_propose to place opening terms, submit a counteroffer, or pass the turn when more detail is needed. Use negotiation_respond to approve or reject terms. Approval must reference the exact subject_hash read from the room, and both parties must approve the same hash for the room to become agreed. Human confirmation is required before ordinary approvals or rejections are sent. A common_ground room sends responses without that confirmation step.

Tools and capabilities

• negotiation_open creates a room and invitation. It accepts a subject schema with initial terms, meeting slots, or general options.
• negotiation_join accepts an invitation and can define the joining side's schema and private limits. It returns the room and any terms already on the table.
• negotiation_list summarizes up to 20 rooms by token, including state, round, turn, and deadline.
• negotiation_read provides the full room state, terms, round history, next action, and human-facing view.
• negotiation_propose submits opening terms, counters, or a request for more detail. Terms must match the proposing side's schema exactly.
• negotiation_respond approves or rejects the current terms, subject to the room's confirmation rules.
• negotiation_cancel withdraws from a room. It can be used out of turn, but closes the room for both parties.

Limitations and notes

Each negotiation_open call creates its own room. An invitation can be answered only once; used, withdrawn, or expired invitations are refused. Cancellation is permanent, and any terms on the table lapse when the room closes.

Negotiation moves are turn-based. Opening terms are allowed only when no terms are on the table, counters can be made only on the caller's turn, and unknown or incorrectly shaped fields are rejected. For meetings, the agreed terms must contain the exact selected slot; a participant's available-time bounds belong in private limits instead.

Use negotiation_propose to continue after seeing terms you do not accept. Rejecting with negotiation_respond ends the room, while cancellation also requires human confirmation except in a common_ground room.