Tools

When you connect Claude, Cursor, Grok, or ChatGPT from Settings, they work this project through these rinkata tools. Talk in plain language; you don't call these by name.

Some writes still wait on you: Accept and Approve. Agents cannot forge those.

Who is who calls the tool: You (human session only), Agent (connected agent), or Either (reads or mode-specific access). Gates and refuse codes live on rinkata_tool_contracts. This page is a directory, not a recipe book.

See the project

Tool	Who	What it does
rinkata_doctor	Either	Run rinkata project health checks.
rinkata_find_artifact_by_external_ref	Either	Foreign→local lookup over the artifact's external_refs[].
rinkata_impact	Either	Read-only multi-hop impact (blast radius) from a Goal section, Spec, Ticket, or Decision root.
rinkata_list_projects	Either	List rinkata projects in the bearer's tenant.
rinkata_read_activity	You	Read the workspace change log, newest first: every change to members, invites, keys, agents, the workspace, projects, repos, Knowledge, requirement changes and feedback.
rinkata_read_artifact	Either	Read any rinkata artifact's frontmatter + markdown body by id or canonical .rinkata path (legacy .plumb paths are also accepted).
rinkata_read_history	Either	Read every change of one Goal, spec, ticket, decision, handoff or idea, newest first and paginated, with its facts in the same timeline.
rinkata_search	Either	Search project artifacts by content BEFORE creating a Goal, spec, or ticket.
rinkata_status	Either	Read project status: counts plus server-computed summaries for orient (top out-of-date work, in flight, recent items).
rinkata_tool_contracts	Either	Read the machine-readable agent contract catalog for every registered rinkata capability.
rinkata_whoami	Either	Who this connection is: { you: { handle, displayName, workspace: { name, tenantId } } }.
rinkata_work_queue	Either	Read an agent-ready work queue combining ticket lifecycle, alignment, blockers, evidence, and health signals.

Ideas

Tool	Who	What it does
rinkata_classify_idea	Agent	Attach an advisory classification to an idea.
rinkata_comment_idea	Agent	Append a comment to an idea WITHOUT altering its captured prose, the way to attach a finding, a correction, or context after capture.
rinkata_create_idea	Agent	Capture a lightweight idea artifact for later triage.
rinkata_idea_set_state	Agent	Set an idea's lifecycle state: archive a captured/triaged idea to dismiss it from the active inbox, or unarchive (restore) an archived idea back to active.
rinkata_list_ideas	Either	List captured idea artifacts from Hub.
rinkata_promote_idea	Agent	Promote an idea into a concrete artifact while preserving the original idea and recording promoted_to provenance.
rinkata_repair_idea_promotion_links	Agent	Repair an idea whose promotion did not finish: link it to the work it became and mark it promoted, so it leaves Ideas.

Knowledge

Tool	Who	What it does
rinkata_knowledge_ask	Either	Ask a question over this project's Knowledge (uploaded docs) with citations.
rinkata_knowledge_create_area	Agent	Create a customer-named Knowledge area in this project and return its areaId for rinkata_knowledge_record, rinkata_knowledge_upload and rinkata_knowledge_move_document.
rinkata_knowledge_list	Either	List this project's Knowledge areas and documents.
rinkata_knowledge_move_document	Agent	Move a listed Knowledge document into another area, or out of an area into Unfiled.
rinkata_knowledge_read	Either	Read one Knowledge document's extracted text and its basis.
rinkata_knowledge_record	Agent	Write a markdown note into Knowledge under an existing customer area, or Unfiled (create an area first with rinkata_knowledge_create_area).
rinkata_knowledge_upload	Agent	Upload a file into this project's Knowledge File Search corpus.

Tickets

Tool	Who	What it does
rinkata_bind_usage_session	Agent	Record that this host session works on a ticket from now, so its measured token usage counts for that ticket.
rinkata_claim	Agent	Claim an assignable artifact for yourself: set its assignee to the caller (the agent principal over stdio, or your tenant-user via Hub).
rinkata_complete_ticket	Agent	Mark a ticket done and record the completion, with optional evidence.
rinkata_create_ticket	Agent	Create a new feature ticket.
rinkata_link_requirements	Agent	Change which approved criteria of its own spec an open ticket covers, under expectedVersion.
rinkata_list_tickets	Either	List tickets filtered by status × goalPath × assignee.
rinkata_preflight_ticket	Either	An advisory read: whether a ticket is safe, out of date, blocked, or unknown. No write requires it, and it never refuses Start or complete.
rinkata_read_ticket	Either	Read a ticket's full frontmatter + markdown body from Hub DB.
rinkata_set_assignee	Agent	Set or clear the assignee on a ticket.
rinkata_set_ticket_source	Agent	Re-anchor an EXISTING ticket onto a Goal (whole body or #section), complements rinkata_set_ticket_spec.
rinkata_set_ticket_status	Agent	Flip a ticket's status (todo, in_progress, blocked, archived).
rinkata_supersede_tickets	Agent	Archive several open tickets as replaced by one surviving ticket, in a single call.
rinkata_update_ticket	Agent	Set a ticket's status (todo, in_progress or blocked), title and assignee in one write, under expectedVersion.
rinkata_update_ticket_dependencies	Agent	Add or remove ticket ids on this ticket's blocked_by in one call.
rinkata_write_ticket_body	Agent	Replace the markdown body of a ticket.

Batches

Tool	Who	What it does
rinkata_create_batch	Agent	Create a batch.
rinkata_list_batches	Either	List batches in this project.
rinkata_read_batch	Either	Read one batch plus shared health (tagged roots, feature progress, blockers).
rinkata_set_batch_phase	Agent	Agents may start, pause, or resume a batch, while close and delete require a human session.
rinkata_update_batch	Agent	Edit an open batch's title, owner, target date or description (the fields the Hub batch drawer edits).
rinkata_update_batch_members	Agent	Add or remove tagged roots on an open batch.

Specs

Tool	Who	What it does
rinkata_approve_spec	Either	A resolved pak_ key may un-park a drafting spec only when that agent created it approved and parked it itself, and no person has approved it since, and an agent's un-park writes no human review stamp.
rinkata_archive_spec	Agent	Archive a spec and apply a downstream policy to its member tickets.
rinkata_create_spec_stub	Agent	Create a lightweight deterministic spec stub anchored at a Goal section.
rinkata_create_standalone_spec	Agent	Create a standalone spec without a parent Goal section.
rinkata_create_successor_spec	Agent	Start a successor spec from a finished one (complete, reopened, or archived), with the earlier spec filled in.
rinkata_extract_spec	Agent	Create a new spec stub anchored at a Goal section.
rinkata_list_specs	Either	List non-archived specs with status, source, ticket count, derived state.
rinkata_migrate_spec_requirements	Agent	Preview existing specs without saving. A person can run the reviewed migration; requirement checks stay off.
rinkata_move_spec	Agent	Move a spec to a different Goal section.
rinkata_plan_from_spec	Either	Per-spec requirement checks: preparing and applying Create/Retire cards when switched on is person-only; planning returns a read-only Review changes view (review + reviewUrl).
rinkata_read_spec	Either	Read a spec's frontmatter + body.
rinkata_set_spec_acceptance	Agent	Replace a spec's typed acceptance: array atomically.
rinkata_set_spec_assignee	Agent	Set or clear the assignee on a spec, the single member accountable for driving it to completion (distinct from the free-form authors[] contributor list).
rinkata_set_spec_sequence	Agent	Set a spec's recommended order hint (sequence: [TICK-…]) through a constrained frontmatter-only write.
rinkata_set_spec_source	Agent	Retarget a spec to a different Goal section.
rinkata_set_spec_status	Either	A resolved pak_ key may un-park a drafting spec only when that agent created it approved and parked it itself, and no person has approved it since, and an agent's un-park writes no human review stamp.
rinkata_set_ticket_spec	Agent	Re-anchor an EXISTING ticket onto a spec, the programmatic equivalent of linking a ticket to a (standalone or Goal-section) spec.
rinkata_write_spec_body	Agent	Replace the markdown body of a spec.

Goals

Tool	Who	What it does
rinkata_approve_goal	You	Constrained Goal governance approve: draft → active.
rinkata_create_goal	Agent	Create a new Goal in Hub DB.
rinkata_list_goals	Either	List Goals filtered by status.
rinkata_migrate_goal_requirements	Agent	Preview or apply suggested requirements for one existing Goal.
rinkata_set_goal_assignee	Agent	Set or clear the assignee on a Goal, the single member accountable for it.
rinkata_write_goal	Agent	Update an existing Goal in Hub DB.

Decisions

Tool	Who	What it does
rinkata_accept_decision	Either	Hub Accept already does this for a person; the tool is for approving a Decision outside Hub. An agent key approves a Decision that agent recorded, or one another agent recorded once it is in effect, when only agents have written to it; a plain proposal from another agent stays with that agent. Hub records the agent and the person it works for. It also accepts a proposed Decision. A retry finishes an approval that did not complete, and keeps the first approver, time and chosen option. An approval recorded from a merged pull request does not accept the Decision.
rinkata_list_decisions	Either	List decisions filtered by lifecycle status.
rinkata_log_decision	Either	Capture a new decision artifact for the project.
rinkata_propose_from_decision	Either	Propose a change review for the work an accepted Decision affects.
rinkata_resolve_decision	You	A person resolves a Decision from their MCP client, as in the Hub UI Decision drawer.
rinkata_update_decision	Either	Update a decision's lifecycle status, owner, structured options, overrides, or supersede-in-state link.

Inbox

Tool	Who	What it does
rinkata_inbox_add	Agent	Capture a new inbox note.
rinkata_inbox_list	Either	List inbox notes.
rinkata_inbox_promote	Agent	Promote a raw inbox note into a tracked ticket and resolve the note in one step.
rinkata_inbox_resolve	Agent	Mark a raw inbox note resolved without promoting it to a durable decision.
rinkata_inbox_set_state	Agent	Transition a raw inbox note to a terminal state: resolved, archived, or discarded.

Handoffs

Tool	Who	What it does
rinkata_amend_handoff	Agent	Append a correction to a handoff WITHOUT replacing or superseding it.
rinkata_list_handoffs	Either	List session handoffs newest-first, filterable by state (default open), about, and query (keyword search over title+body+id).
rinkata_read_handoff	Either	Read a session handoff.
rinkata_set_handoff_state	Agent	Transition a handoff one-way: open→consumed (stamps consumed_at/consumed_by), open→archived, or consumed→archived.
rinkata_write_handoff	Agent	Stash a session-handoff prompt for the next session/context window.

Out of date

Tool	Who	What it does
rinkata_apply_staged_reconcile	Either	Apply a change review (Goal→Spec or Spec→Ticket) after a person approves that concrete plan. An agent key applies only the review of a Decision that agent wrote every version of, or logged or accepted while it is in effect and only agents wrote it, and Hub records the agent and the person it works for. A review that archives work or reopens a finished ticket still needs a person.
rinkata_list_drift	Either	Read out-of-date tickets for the current rinkata project.
rinkata_propose_reconcile	Either	Compute the current change-review proposal without writing files.
rinkata_propose_staged_reconcile	Agent	Propose a two-stage (Goal→Spec or Spec→Ticket) change review for a target, same semantics as the Hub UI Out of date drawer.
rinkata_read_drift_proposal	Agent	Read a stored change review.
rinkata_reconcile_apply	You	Apply a Hub change review only after explicit human approval of that concrete plan.
rinkata_reconcile_write	Agent	Write a Hub change review as a review artifact.

Mismatches

Tool	Who	What it does
rinkata_list_drift_findings	Either	Read the mismatches Hub found when work completed, merged or deployed, each with its cause and who resolved it. It also says whether a tenant admin turned the checks off for the project (they are on until then), how the last check went, how many are open, and when they are piling up.
rinkata_resolve_drift	Either	Resolve one mismatch Hub found: a bug ticket under active work, a Decision that replaces the old one, or the safer option flagged for a person.

Complete

Tool	Who	What it does
rinkata_begin_demo_screenshot_upload	Agent	Start an out-of-band Demo Pack screenshot upload.
rinkata_complete_spec	Agent	Complete a spec (verify member tickets are done/archived).
rinkata_finalize_demo_screenshot_upload	Agent	Finish an out-of-band Demo Pack screenshot upload after the curl PUT.
rinkata_list_demo_reviews	Either	List the actionable Demo Pack review queue from Hub.
rinkata_propose_demo_evidence	Agent	Attach completion evidence for a spec from an agent or API-key context.
rinkata_read_demo_pack	Either	Read a spec's Demo Pack readiness projection from Hub.
rinkata_set_spec_demo_required	Agent	Toggle a spec's demo_required policy flag through a constrained frontmatter-only write.

More

Tool	Who	What it does
rinkata_confirm	You	Records the person's tap on Rinkata's confirm card (MCP Apps).
rinkata_create_project	You	Create a draft project (no repository) in your own workspace; the workspace is always the caller's.
rinkata_draft_review_rewrite	Agent	Attach an agent-drafted ticket body to an Update action on a stored review.
rinkata_list_agents	Either	List agents in the bearer's tenant (GOAL-PLUMB-4).
rinkata_list_gate_events	Either	Read the human-gate ledger rows for one subject (spec, Goal, ticket, or Decision id), oldest first, with every column.
rinkata_list_users	Either	List users in the bearer's tenant.
rinkata_project_list_repos	Either	List the repos attached to a rinkata project, primary first.
rinkata_rank_anchor_repair	Either	S4 / TICK-PLUMB-942: rank section-anchor repair candidates for a ticket or spec with a broken/tombstoned/suspect source_anchor_id.
rinkata_read_hub_image	Either	Fetch one HubImage as MCP ImageContent so agents can vision-read a design attached to an idea (or rehomed onto a Goal/spec/ticket).
rinkata_record_human_approval	You	Human-only: stamp a durable human review approval on a Goal or drafting spec, bound to current version+graphHash.
rinkata_record_requirement_exception	You	Record, renew, or end a person-only exception.
rinkata_repair_task_graph	Agent	Repair task-graph inverse edges by making blocks and blocked_by mirror each other.
rinkata_set_requirement_mode	Agent	Switching on is person-only. Switching off is allowed for agents.
rinkata_submit_feedback	Agent	Volunteer free-form feedback about using rinkata itself, friction, a confusing error, a surprising or great result.
rinkata_work_changes	Either	Read what changed for your work since a cursor, plus the project's Knowledge changes (an area created, a document move) as events with source knowledge.

See also

• The four panels
• Agents: ceremony and confused pairs
• Claude · Grok · Cursor · ChatGPT