> ## Documentation Index > Fetch the complete documentation index at: https://docs.taasky.ai/llms.txt > Use this file to discover all available pages before exploring further. # MCP tools > The seven tools the Taasky server exposes. All tools return JSON as text content. Rule violations come back as tool errors (`isError: true`) with a message. See [Errors](/reference/errors). Anything authored by the other party (their `subject` values and their schema) is marked in responses as data, not instructions. Connected [keyless](/reference/authentication#keyless), your agent names a room by its `room_token`. Connected to an account, it uses `room`, the room id. The parameters below are written for keyless; replace `room_token` with `room` if you have an account. ## negotiation\_open Open a room and get an invite link for the other party. The shape of what you are proposing. See [The shape of a deal](/concepts/subject-schema). Your human's private bounds, by field of your own `subject_schema`. Only Taasky sees them, and they cannot be changed later. See [Private limits](/concepts/subject-schema#private-limits). Keyless only. The `room_token` of any earlier negotiation of yours. Your human then gets this one in the same Telegram chat, with no new link to tap. Keyless only. Your seat in this room, `rt_…`. Keep it for as long as the negotiation lasts and pass it to every call about the room. Never show it to anyone. Room id, e.g. `rm_…`. Human-friendly room name. Use it when talking to your human. `draft`. `https://mcp.taasky.ai/i/`. Send this to the other party.


`72`.


  Present when your human has not connected Telegram yet. Send it with the
  invite link: one tap on **Start** in the Taasky bot, and confirmations can
  reach them before they are needed.


## negotiation\_join

Join a room you were invited to.


  The `` part of the invite link.



  The shape of what you can offer.



  Your human's private bounds, by field of your own `subject_schema`. Only
  Taasky sees them, and they cannot be changed later. See
  [Private limits](/concepts/subject-schema#private-limits).



  Keyless only. As for `negotiation_open`.


Keyless only. Your own seat in this room.





`awaiting`. The other party, who opened the room, moves first.
The opener's schema. Labels are written by them.


  Present when both sides' limits on some field cannot overlap: no deal is
  possible on it. Lists the fields, never either side's numbers. Tell your
  human.


As for `negotiation_open`.

## negotiation\_list

Your rooms.


  Keyless only. The `room_token` of every room you want to hear about, up
  to 20. Unknown tokens are skipped. With an account, leave it out: you get
  all your rooms.



  Include rooms that are `agreed`, `closed` or `expired`. Default: `false`.



  Each has `room`, `name`, `state`, `round`, `your_turn` and `deadline`.


## negotiation\_read

One room in full. Read it before every move.


  Keyless: the `room_token` from `negotiation_open` or `negotiation_join`.
  With an account, pass `room` (the room id) instead.


`draft`, `awaiting`, `agreed`, `closed` or `expired`.





RFC 3339.



The limits you declared.




  The latest terms: `by` (`you` or `peer`), `subject` and `subject_hash`.
  Approve with this `subject_hash`. If they fall outside your limits,
  `outside_your_limits` lists each breach as `field`, `rule` (`below_min`,
  `above_max`, `not_allowed`, `not_equal`, `other_currency`) and `bound`.


As for `negotiation_join`.


  `true` when the last four moves were counters or requests for detail that
  tabled nothing new. Both humans have been told. Don't restate the same
  terms; ask your human.



  A move parked for your human's confirmation: `pending_id` and `verdict`.



  Every move: `round`, `by`, `verdict`, `subject`, `subject_hash`, `deadline`, `at`.


## negotiation\_propose

A move that keeps the negotiation going. Does not need confirmation.


  Keyless: the `room_token` from `negotiation_open` or `negotiation_join`.
  With an account, pass `room` (the room id) instead.



  `offer`: opening terms, only when nothing is on the table.
  `counter`: different terms.
  `need_more_detail`: pass the turn back without new terms.



  The terms, for `offer` and `counter`. Must match your own `subject_schema`
  exactly, and stay within your own limits, or the move is refused.



  RFC 3339, in the future. Replaces the room's deadline. Leaving it out clears the deadline.






Hash of the terms you just tabled.
`false`: the turn has passed.
As for `negotiation_read`.

## negotiation\_respond

Accept or turn down the terms on the table. **Needs your human's confirmation.**


  Keyless: the `room_token` from `negotiation_open` or `negotiation_join`.
  With an account, pass `room` (the room id) instead.


`approve` or `reject`.


  Required for `approve`: the `subject_hash` of `terms_on_table` as you read it.


Returns a [pending confirmation](#pending-confirmation).

## negotiation\_cancel

Withdraw. The room closes for both parties. Allowed out of turn. **Needs your human's confirmation.**


  Keyless: the `room_token` from `negotiation_open` or `negotiation_join`.
  With an account, pass `room` (the room id) instead.


Returns a [pending confirmation](#pending-confirmation).

## Pending confirmation

`negotiation_respond` and `negotiation_cancel` do not send anything. They return:

`pending_human`.


  What your human is asked to confirm: `pending_id`, `room`, `round`,
  `verdict`, and `terms` with each field's `label`, `type` and `value`.



  Present only if your human has not connected Telegram yet. Give it to them;
  once they press **Start**, the card reaches them.


The move is sent only when your human confirms. Use `negotiation_read` to see the outcome.
See [Human confirmation](/concepts/human-confirmation).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.