---
title: "Tools reference"
description: "All 16 Cadence MCP tools, generated from the versioned operation registry."
canonical_url: https://cadence-me.com/developers/tools
last_updated: 2026-10-18
status: stable
source: src/data/developers.ts
---

# Tools reference

The reference and examples are generated from contract 1.7.0. Each page lists input and output fields, permissions, annotations and errors. Examples use synthetic records and validate against contract fixtures.

## Read and write tools

- [get_account_context](/developers/tools/get_account_context): Get Cadence account context.
- [list_behaviors](/developers/tools/list_behaviors): List Behaviors.
- [get_behavior](/developers/tools/get_behavior): Get Behavior.
- [list_categories](/developers/tools/list_categories): List categories.
- [get_timeline](/developers/tools/get_timeline): Get Timeline.
- [list_occurrences](/developers/tools/list_occurrences): List Occurrences.
- [get_occurrence](/developers/tools/get_occurrence): Get Occurrence.
- [list_day_notes](/developers/tools/list_day_notes): List day notes.
- [get_adherence_summary](/developers/tools/get_adherence_summary): Get adherence summary.
- [search](/developers/tools/search): Search Cadence.
- [fetch](/developers/tools/fetch): Fetch Cadence record.
- [set_occurrence_status](/developers/tools/set_occurrence_status): Set Occurrence status.
- [set_parent_occurrence_status](/developers/tools/set_parent_occurrence_status): Set parent Behavior slot status.
- [update_occurrence_note](/developers/tools/update_occurrence_note): Update Occurrence note.
- [move_occurrence_for_day](/developers/tools/move_occurrence_for_day): Move Occurrence for today.
- [revert_occurrence_move](/developers/tools/revert_occurrence_move): Undo Occurrence move.
- [update_day_note](/developers/tools/update_day_note): Update day note.
- [add_opportunity_occurrence](/developers/tools/add_opportunity_occurrence): Add opportunity to today.
- [remove_opportunity_occurrence](/developers/tools/remove_opportunity_occurrence): Remove added opportunity.
- [create_behavior](/developers/tools/create_behavior): Create Behavior.
- [update_behavior](/developers/tools/update_behavior): Update Behavior.
- [archive_behavior](/developers/tools/archive_behavior): Archive Behavior.
- [restore_behavior](/developers/tools/restore_behavior): Restore Behavior.
- [end_behavior](/developers/tools/end_behavior): End Behavior now.
- [pause_behavior](/developers/tools/pause_behavior): Pause Behavior.
- [resume_behavior](/developers/tools/resume_behavior): Resume Behavior.

## Confirmation

Read tools are read-only. Existing-record writes carry destructiveHint=true; create_behavior is non-destructive but still needs the user's direction. Annotations inform the host client. They are not a server-side confirmation dialog or a replacement for permission checks.

## Maintaining the reference

The registry owns schemas, descriptions, scopes and annotations. Update its fixtures alongside a contract change. Run npm run developers:check -- --write to regenerate the reference, then npm run developers:check to detect drift. Marketing checks enforce the same check.
