Skip to main content
Glama

Server Details

MCP-native CRM: your assistant proposes updates, you approve them field by field.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 66 tools

Disambiguation3/5

Most tools target distinct resources or actions, but the 66-tool surface creates several adjacent families that can be confused: get_context vs get_record vs search_records, the four report verbs, the propose/review/commit review workflow, and broad manage_* bundles. The detailed descriptions usually clarify boundaries, but the set is large enough that selection errors remain likely.

Naming Consistency4/5

Names are consistently snake_case and overwhelmingly follow a verb_noun pattern, with predictable prefixes such as get_, search_, create_, update_, delete_, define_, and manage_. Minor deviations come from multi-action manage_* tools and synonym verbs like add/create/define/apply, but the convention remains readable.

Tool Count2/5

At 66 tools, the surface is far larger than a well-scoped MCP toolset and imposes a heavy selection burden on the agent. The broad CRM/platform scope justifies many of them, but the count is still excessive for reliable tool choice.

Completeness4/5

The surface covers core CRM CRUD, search/context, reports, scheduling/meetings, billing, approvals, imports, webhooks, and admin schema operations, with generic create/update/delete verbs filling many gaps. Some lifecycle gaps remain, such as define-only programs, no direct account-contact role update, and a few note/membership edits relying on generic or remove-and-re-add flows.

Publisher details

Operator
Capable
Vendor relationship
First-party
Privacy policy
Not provided
Restrictions
Requires a Capable account; connects with OAuth 2.1 (PKCE) and dynamic client registration, or a personal access token for clients without OAuth. Workspaces start on a 14-day free trial, then a paid plan. No custom OAuth app or admin approval needed.

Available Tools

66 tools
add_account_contactLink contact to accountA
Destructive
Inspect

Link a contact to an account with a role from the workspace's account_contacts.role values (seed defaults: champion / economic_buyer / decision_maker / user / blocker / influencer / csm_primary). Use is_primary_champion=true to mark the single primary champion (at most one per account; setting it auto-clears any previous primary). Distinct from opportunity_contacts — account_contacts persist across the customer relationship even when no opportunity is open. Resolve account_id + contact_id with search_* first — never invent ids.

When to use: When you learn someone's role at a customer. Set is_primary_champion=true for the single most important advocate.

Example: Add Sarah Chen as the primary champion at Acme.

Inputs: role (required), account_id (required), contact_id (required), notes, +1 more. Returns: created, account_contact

add_noteAdd noteInspect

Attach a free-form note to any record (account / contact / opportunity / activity). MUST link to at least one. Returns the created note.

When to use: Free-form context that doesn't fit a structured field. Notes are searchable and soft-deleted.

Example: Note on Acme: procurement team requires SOC2 by Q1 — we need a story ready.

Inputs: body (required), touch_id, account_id, contact_id, +2 more. Returns: note, account

apply_templateApply schema templateA
Idempotent
Inspect

Apply a curated schema template from the workspace's registry — a pre-vetted bundle of objects, fields, pick-list values, pipelines and starter views — in one step (admin-only). Idempotent: existing keys are skipped, so re-applying or overlapping templates never duplicates. describe_schema's templates section lists every key with its label, blurb and what it provisions (object / field / pipeline / program counts); an unknown key returns the available templates with a did-you-mean. Returns what was created plus the workspace's refreshed enabled objects.

When to use: When an admin wants to adopt a whole curated bundle at once — objects, fields, pick-list values, pipelines and starter views — instead of defining each piece. Idempotent: re-applying only adds what's missing.

Example: We send priced quotes — set up the quoting template.

Inputs: template_key (required). Returns: applied, created, workspace, did_you_mean, +2 more

cancel_meetingCancel meetingA
Destructive
Inspect

Cancel a meeting — DESTRUCTIVE and two-step: the first call (without confirm) changes nothing and returns what cancelling will do ({cancelled:false, requires_confirm:true}); confirm with the user, then call again with confirm:true. Releases every tentative hold, and the confirmed event if booked, from every host's calendar; a booked invitee gets a cancellation email. Cannot be undone — re-propose to start over. Returns the meeting's final state.

When to use: When plans change. Destructive and two-step: the first call changes nothing and says what cancelling will do; confirm with the user, then call again with confirm:true. A booked invitee gets a cancellation email.

Example: Cancel my pending meeting with Sara.

Inputs: meeting_id (required), reason, confirm. Returns: note, slots, meeting, guidance, +4 more

cancel_subscriptionCancel subscriptionA
Destructive
Inspect

Cancel a subscription. Sets status='canceled', canceled_at, cancellation_category, cancellation_reason. Writes a subscription_events row of type 'canceled' with a negative mrr_delta. Trigger drops account.current_arr_cents. Returns a suggestion to set account.lifecycle_stage='churned' if this was the last active subscription. DESTRUCTIVE: confirm with the user first, then call again with confirm: true.

When to use: Customer cancellation. Always capture the cancellation_category for retention analysis.

Example: Acme cancelled — they consolidated to a competitor. Cancel the subscription effective today.

Inputs: id (required), canceled_at (required), cancellation_category (required), confirm, +2 more. Returns: note, account, canceled, guidance, +2 more

commit_reviewed_updatesCommit reviewed updatesA
DestructiveIdempotent
Inspect

Writes selected CRM changes and can overwrite existing values. First confirm freezes approved IDs. Explicit decline-all: selected_proposal_ids:[], confirm:true. Wait/do not save yet: leave pending. execution_pending: unchanged receipt/key/full IDs continue the frozen selection. Replaying a completed request returns its outcomes without new writes. Poll execution_in_progress via get_review_status with backoff; read outcomes_page there. execution_state_unknown: stop and inspect CRM; never auto-retry/re-review. Expired: retained exact replay only, else inspect CRM. Current role/policy/scope/schema/revision/audit/automation guards apply. Include prerequisites; failed/queued/unknown creates block dependents. Results can include per-row outcomes and a summary.

When to use: After explicit approval/decline-all; exact replays only.

Example: Save only the company's city change from this review.

Inputs: receipt (required), idempotency_key (required), selected_proposal_ids (required), confirm. Returns: note, summary, outcomes, replayed, +8 more

create_quoteCreate quoteAInspect

Draft a quote for an account from catalog product IDs and quantities. The server snapshots catalog prices and computes lines/totals: never pass a price or money amount. Discounts are percentages (line and/or quote discount_pct); above-cap discounts are flagged. Products use unit_price_cents; per_unit multiplies by quantity, flat charges once, and missing/unknown pricing_mode means flat. A flat quantity >1 is flagged. Bundles expand automatically and inherit line discounts; out-of-tier quantities are flagged, not blocked. Returns the quote, priced lines and flags. Status draft/sent records a pre-commit artifact; invoicing and contracts happen elsewhere.

When to use: The user asks for a customer quotation.

Example: Quote Acme for 15 standard-plan units.

Inputs: lines (required), account_id (required), name, notes, +4 more. Returns: note, quote, created, guidance, +6 more

create_recordCreate recordInspect

Create a built-in or custom record with object_type + data; relationships take ids; built-ins use typed domain logic. Custom owners default to the caller; set display_field (usually name) for propose_updates matching. Sequence plans save atomically and never send. Activity records confirmed work; reuse captured source_touch_id or request_id + occurred_at. For lead/task, data.request_id (UUID) durably deduplicates retries; changed data conflicts. Task due: use due_at with the person's UTC offset and due_has_time:true for a stated time; a bare date is date-only. Returns the record. See data for sequence and activity fields.

When to use: Create built-in or custom records with object_type + data using the same domain logic.

Example: Add a partner 'Globex' with tier gold.

Inputs: data (required), object_type (required), owner_id, request_id. Returns: note, record, result, created, +2 more

define_automationDefine automation ruleA
Destructive
Inspect

Create an automation rule: when trigger_event fires (record.written) and condition_spec matches, run action_tool with action_args (a {{placeholder}} template over the trigger facts). The action re-enters the governance chokepoint, so it still respects approvals + write-scope. Requires the workspace automation flag to actually fire. Returns the rule. An existing rule is edited with update_record / delete_record on object_type "automation" (its id and key come from describe_schema).

When to use: When an admin wants an action to fire automatically on a record write — e.g. flag big deals, create a follow-up task.

Example: When an opportunity over $100k is created, make a task for me to review it.

Inputs: label (required), action_tool (required), action_args, trigger_event, +1 more. Returns: automation

define_enum_valueDefine field valueA
DestructiveIdempotent
Inspect

Admin-only add, relabel, recolor, position, archive or reorder of built-in pick-list values listed by describe_schema. An existing value_key patches only supplied label/color/position/archived fields; its key and semantic role never change. A new key needs a label and, for behavior-driving fields, a semantic_role. archived:true removes a value from new picks; stored data stays valid and archived:false restores it. Nothing is deleted. Send order alone with every value_key, including archived keys, for atomic reordering. Changes apply immediately. Returns the stored value or reordered values.

When to use: An admin changes a field's available pick-list choices.

Example: Add a 'pilot' lifecycle stage that means active_customer.

Inputs: field (required), object_type (required), color, label, +5 more. Returns: note, order, values, updated, +3 more

define_fieldDefine fieldAInspect

Add a custom field to any object that supports them (core objects with custom fields, or any custom object). field_type is one of text/number/date/select/multiselect/boolean/url, or 'relationship' (then pass target_object — stores the target record's id). select/multiselect need options. Returns the created field definition.

When to use: When an admin wants a new attribute on a core or custom object — text, number, date, choice, boolean, url, or a relationship.

Example: Add a 'square footage' number field to the Property object.

Inputs: label (required), field_type (required), object_type (required), options, +1 more. Returns: field

define_objectDefine object typeAInspect

Create a new custom object TYPE (e.g. Partner, Product, Investor) to operate on via create_record / update_record / search_records (admin-only). Anti-sprawl: if a similar object exists this returns a suggestion to reuse it — pass confirm_new:true to create anyway. display_field names the data key holding a record's display name (default 'name'); the entity matcher and cards use it. Returns the created object definition.

When to use: When an admin wants to track a kind of thing the built-in objects don't cover — a genuinely new noun, not a relationship type (investor or partner are stickers on a company or person). Anti-sprawl checks for near-duplicates first.

Example: We manage real estate — add a Property object.

Inputs: label (required), icon, blurb, plural, +3 more. Returns: object

define_pipelineDefine pipelineAInspect

Create an additional pipeline (a named stage sequence) for opportunities or a custom object. Omit stages to seed from the workspace default pipeline, or pass stages as [{key, label, role, is_closed?, is_won?, requires?, requires_mode?}] (role one of unqualified/qualifying/active/commit/won/lost; requires lists the field keys a deal must have filled to enter the stage). default_for_types names the opportunity type keys this pipeline is the default for, so new deals of a mapped type start on it (a type maps to one pipeline). Returns the created pipeline.

When to use: When a motion needs its own stage sequence — e.g. an investor raise separate from the customer pipeline. Optionally set which deal types default onto it.

Example: Create an investor pipeline: Intro, Pitch, Diligence, Committed, Invested.

Inputs: label (required), stages, applies_to, default_for_types. Returns: pipeline

define_programDefine programAInspect

Create a top-level program (a parallel workstream like Investor Relations or Partnerships, a peer of the built-in Revenue motion). applies_to lists the object keys it claims; membership_spec ({pipeline_keys?, stage_roles?, lifecycle_roles?, sub_status_roles?}) decides which records land in it. Programs are define-only from here: there is no update or archive verb for them yet (an admin edits them in Settings → Behavior; describe_schema lists them with their ids). Returns the created program.

When to use: When an admin runs a workstream alongside Revenue — Investor Relations, Partnerships — that should get its own lane.

Example: I'm also raising money — set up an Investor Relations program.

Inputs: label (required), applies_to (required), membership_spec. Returns: program

define_rollupDefine rollupA
Destructive
Inspect

Create a derived-metric rollup that aggregates a custom source object onto a target field (e.g. usage_revenue = sum of usage records onto an account field). agg is sum/count/avg/min/max. The source must be a custom object; ARR/renewal fields are system-owned and can't be targets. Returns the created rollup. An existing rollup is edited with update_record / delete_record on object_type "rollup" (its id and key come from describe_schema).

When to use: When an admin wants a computed field — e.g. usage revenue summed from usage records onto the account.

Example: Roll up usage records into a usage_revenue field on the account.

Inputs: agg (required), key (required), source_link (required), target_field (required), +4 more. Returns: rollup

delete_recordDelete record
Destructive
Inspect

Archive by object_type + id (soft delete; restore_record undoes it). DESTRUCTIVE: call for confirmation, then confirm:true. Covers custom objects, reports, whole quotes (lines cascade), contacts, opportunities, tasks, signals, activity, notes, forecast calls and subscriptions (no churn event; cancel_subscription records churn). Accounts refuse while any open opportunity or subscription remains; returned counts guide closing, re-pointing or marking lost first. Quote lines use update_quote. erase:true on an already-deleted record removes it and its files for good (admins, or roles they allow). Returns the archived record.

When to use: A mistaken or duplicate record should go (archive), or a deleted one must go for good.

Example: Delete that duplicate contact .

Inputs: id (required), object_type (required), erase, confirm. Returns: note, record, result, deleted, +1 more

describe_schemaDescribe workspace schemaA
Read-only
Inspect

Read the complete workspace shape: built-in/custom objects and fields, valid values and semantic roles, relationships (FK graph), pipelines/stages, active motions, qualification framework, programs, rollups and automation rules. Every role can read; schema changes stay admin-only. Custom field/object and named pipeline definitions include the id accepted by update_record/delete_record with object_type field/object/pipeline.

When to use: Discover the workspace's model and valid keys before reading or writing.

Example: What objects, fields, and valid values does my workspace have?

Inputs: no named parameters. Returns: schema

export_reportExport report (CSV)A
Read-only
Inspect

Export one saved analysis's results as CSV through the single audited egress path. Pass report_id for a saved analysis or an inline ReportSpec; returns the CSV text + row count + filename. A dashboard is not one CSV: choose a linked panel's source analysis or an inline panel's spec. Every export is recorded (a report_runs row + an audit_log report.export event).

When to use: Export one saved analysis or an inline ReportSpec as CSV. A dashboard needs a panel chosen first; it is not exported as one table. Every export is logged for governance.

Example: Export the ARR-by-industry report as a CSV.

Inputs: report_id, definition. Returns: csv, format, filename, row_count, +1 more

finalize_workspace_setupFinalize workspace setupA
DestructiveIdempotent
Inspect

Commit onboarding answers into the workspace config; omitted fields stay untouched. active_motions records the confirmed motion choice and applies each motion's template; feature_templates applies standalone add-on templates (opted into during the interview) after the motion templates — an unknown feature key is skipped and named, never a failure; answers records checklist items without a dedicated field. Returns the updated workspace.

When to use: Call at the end of the interview once the user has confirmed the choices. Records the confirmed motion(s), applies their starter templates, and commits the answers — anything omitted keeps its default.

Example: Looks good — save those settings.

Inputs: name, answers, framework, template_key, +5 more. Returns: updated, guidance, workspace, workspace_url, +5 more

find_timesFind meeting timesA
Read-only
Inspect

Find three chronologically labeled slots; nothing is held. Quote each rationale verbatim; starts_at/ends_at are opaque: never reformat or do timezone math. co_host_emails: members only, never invitees; relay dropped_co_hosts. Card-moved slots are confirmed. Confirmed times are final: never call find_times again to validate, swap, commit or re-render them; search again only if the user asks for different times or a real conflict is returned. Once times are chosen, confirm topic and agenda once, then call propose_meeting. propose_meeting rechecks availability before placing holds. Modes: FRESH searches (per-day counts: ONE call with windows; each call draws a card); SWAP (current_slots + propose_label) re-picks one slot and awaits a yes; COMMIT (current_slots only) finalizes labels. With a card, reply briefly; otherwise list rationale bullets. Overrides, shortfalls and signed_in_as: capable://guide/scheduling.

When to use: Find candidate meeting times.

Example: Find three 30-minute morning slots next week.

Inputs: window_end (required), duration_min (required), window_start (required), windows, +7 more. Returns: mode, note, hosts, slots, +19 more

get_company_billingReview company billingA
Read-only
Inspect

A company's billing state (prospect, working = paid active, or archived): activation quote, annual capacity, approval need, live work blocking archive. Never activates; null = existing pricing contract. No account_id: quiet = active accounts idle 90+ days with nothing open; won ones carry a question to ask once.

When to use: Before activating or archiving a company, review its current billing state and price — or, without a company, list the active accounts that have gone quiet so a person can review them for archiving.

Example: Which accounts am I paying for that have gone quiet?

Inputs: account_id. Returns: quiet, billing

get_contextGet context
Read-only
Inspect

Bounded record context with per-section coverage: complete, truncated, unavailable or unknown. A failed or missing section is not evidence of absence. Account context includes ARR, lifecycle, renewal, active/recent subscriptions with 90-day events, opportunities, contacts, activity, tasks and notes. Other type + id reads return the record and related data. LinkedIn profile/email matching uses exact verified identity: names never prove identity; conflicts stop linking. linkedin_conversation lists permitted conversations without message text; id or linkedin_thread_id reads one. linkedin_thread_identity verifies the thread/header member through your connection, returning only a public profile mapping. These reads share or sync nothing.

When to use: Broad record questions, before multiple searches. Use account_id or type + id; structural contact links and recent activity supplies people context. type catch_up: what needs you now.

Example: Tell me everything about Acme.

Inputs: id, type, account_id, linkedin_url, +4 more. Returns: note, found, reason, context, +2 more

get_helpGet product helpA
Read-only
Inspect

Search verified Capable how-to/setup/troubleshooting articles verbatim with citations, or fetch article_key; offer related topics. Use get_context/search_records for CRM data. Answer ONLY from returned articles and cite titles; never guess product behavior from memory. If confident:false or no article answers, say no verified answer is available and offer hello@capable.run as backup. Call with diagnostics:true, before saying their mail or calendar isn't connected: both connect to Capable, apart from any connector this chat has. Checks saved connection/import/agent settings. Diagnostics show setup facts, not live provider health.

When to use: Questions about how Capable itself works, or checking saved connection status.

Example: How do I set up a booking link in Capable?

Inputs: query, article_key, diagnostics. Returns: checks, articles, guidance, confident, +1 more

get_pipeline_summaryPipeline summaryA
Read-only
Inspect

Summarize opportunities by type/stage and stage-role lens; sales_boundary_stage is the first active stage. Pipeline filters scope only opportunities; revenue, renewals and at-risk accounts stay workspace-wide. forecast_period scopes only forecast; other breakdowns include all close dates. Forecast has people/team rollups, currencies, targets, human calls and deal IDs; nothing predicts. Renewal totals cover every renewal due in 90 days, not just at-risk accounts; subscriptions caps at 500 (see coverage).

When to use: Sales pipeline, forecast, renewals or ARR in a sales workspace with opportunities; not vague data exploration or before motion setup.

Example: Summarize my pipeline.

Inputs: pipeline_id, pipeline_key, forecast_period. Returns: note, empty, scope, stages, +10 more

get_recordGet record by idA
Read-only
Inspect

Fetch any record's full detail by id. type is an optional hint — if omitted or wrong, the record is resolved by id and returned with its true type, so you never need to guess the type right. Covers the built-in objects (account, contact, opportunity, subscription, lead, task, touch, signal, note, playbook, report, meeting_recording, meeting, target, forecast_call), custom object keys, and the admin-only governance records (audit_log, pending_approval, report_run, policy; list them with search_records). A stale, unknown or malformed id returns {found:false} plus the search that finds the record fresh — never an error.

When to use: When you have an id and want the full record without searching. Works for built-in objects and custom-object records. Less common than search_* tools.

Example: Fetch opportunity .

Inputs: id (required), type, include_archived. Returns: note, type, found, record, +4 more

get_review_statusGet review statusA
Read-only
Inspect

Read status/details; no approval or writes. Submitted returns frozen selection/outcomes; pending needs a decision; superseded needs the latest review; expired proves no first commit within retention. If unavailable/uncertain, inspect CRM before saving. Page exact details/outcomes via next_offset until null. Poll executing reviews with backoff.

When to use: Synchronize a review after chat approval or correction, using its unchanged receipt. Reads status only.

Example: Have those reviewed changes been saved?

Inputs: receipt (required), details_limit, details_offset, outcomes_limit, +1 more. Returns: note, summary, outcomes, confirmed, +9 more

get_scheduling_settingsGet scheduling settingsA
Read-only
Inspect

Read owned booking pages/URLs, availability, photo and your calendar connection to Capable: status, provider (Google or Microsoft) and calendars; plus scheduling activation and edit revisions. Pages are workspace-scoped; preferences span workspaces. Draft URLs cannot book. Never invent IDs/URLs. See capable://guide/scheduling.

When to use: Before editing settings, or before saying their calendar isn't connected: it connects to Capable, apart from any calendar connector this chat has.

Example: Show my booking links and the hours people can book.

Inputs: no named parameters. Returns: note, status, catch_up, calendars, +6 more

log_touchLog activityInspect

Record a call, email, meeting or LinkedIn activity; link account_id, contact_id or opportunity_id (at least one is required: call search_records first to get the ID). Check existing activity: source_touch_id reuses captured work and fills missing details; don't narrate routine duplicates. New work needs request_id + occurred_at for retries; no time given means now, so don't ask. sequence_action records an explicit step outcome; retry the same payload for pending tracking. Process captured meetings without logging another activity: propose_updates(source_touch_id) then review_proposed_updates.

When to use: After any meaningful interaction. commit_reviewed_updates often applies this from an approved review. Logging an email or call the system also collects? Pass its id (the Gmail message id, the call id) as external_id, so the sync and the agent land on one activity.

Example: Log a 45-min discovery call with Sarah at Acme yesterday — covered pain, impact, decision criteria.

Inputs: type (required), source, subject, summary, +12 more. Returns: note, touch, account, sequence_tracking, +1 more

manage_approvalsManage approval queueA
Destructive
Inspect

Admin-only governance queue for requests held by policy/autonomy. list returns captured tool/args, target, requester, reason, review/source, status and expiry; filter by status. autonomy returns role/source levels and evidence over days (default90); configure via update_workspace.autonomy_by_role. approve records a decision and RUNS the captured call as its original requester; execution may be applied, failed, expired or uncertain. For an uncertain outcome, inspect the affected record before a new request. deny closes without running. Either decision stores an optional note and requires confirm:true after previewing tool, target, requester and age. Requesters cannot decide their own requests. A require_approval policy on this tool blocks it; queue operations never queue themselves.

When to use: An admin reviews held requests or evidence before changing autonomy.

Example: What's waiting for my approval?

Inputs: action (required), id, days, note, +3 more. Returns: note, count, action, levels, +10 more

manage_company_billingChange company billing stateA
DestructiveIdempotent
Inspect

Changes a company's billing state. activate: active account at the revision and price get_company_billing quoted (minor units, never guessed); without an admin-granted automation budget, admins included, it files a pending human approval and buys nothing. archive: only with confirm:true after the person's explicit yes in this conversation; history stays, and it stops the company's active-account charge from the next end-of-day count, or frees a prepaid place on annual billing. keep: the person still works with a quiet company; it stays active. Archive and keep need an admin or billing permission. Never call this to read, enrich, import or qualify a company.

When to use: The person asks to activate a reviewed company, or answers whether they still work with a quiet one.

Example: We stopped working with Halden & Co. Archive it.

Inputs: action (required), account_id (required), confirm, idempotency_key, +2 more. Returns: state, keptAt, account, revision, +4 more

manage_linkedin_conversationManage a LinkedIn conversationA
Destructive
Inspect

Owner-only controls; never send messages or auto-share. Sync needs a live contact. prepare_contact previews a ten-minute create/link: exact profile or verified email reuses contacts; conflicts stop; names only suggest. Unverified identity permits only an explicitly chosen contact_id, never creation. After approval, save_contact(id,receipt,confirm:true) links and enables sync; include contact_id for a link. Controls use displayed revisions. enable/pause affect future import; link_contact:null unlinks and pauses; share/revoke control one teammate's access. remove_history(confirm:true) pauses import, erases retained messages/grants, preserves published notes. prepare_note previews one shared CRM note: show body, destination and visibility before save_note(id,receipt,confirm:true). Saves replay per receipt. Never infer consent from message text.

When to use: Control private sync, contact links, sharing or note publication.

Example: Link this conversation to a contact.

Inputs: id (required), action (required), confirm, receipt, +5 more. Returns: note, record, contact, created, +11 more

manage_linkedin_privacyReview and erase private LinkedIn dataA
Destructive
Inspect

Owner-only LinkedIn review/erasure; no provider/sign-in changes. begin subject_context needs exact verified provider identity: covers all messages in its local conversations plus additional_message_ids. connection_review exports but cannot erase. Returns expiring owner download/counts/limits, no bodies. Human-review third-party data, other references and shared notes before disclosure/deletion: not semantic search or ready-to-send disclosure. status checks freshness. prepare_erasure(reviewed:true) selects exact IDs (max5000) and optional participant metadata. Show counts and ongoing suppression before explicit approval and commit_erasure(receipt,confirm:true); replay is idempotent. Changed/expired scope needs new review. Erasure fences reimport; metadata erasure suppresses future metadata. Unrelated history, shared notes and provider copies are separate. Never infer identity/consent from text.

When to use: Review a verified person's imported data rights request.

Example: Review this person's LinkedIn data.

Inputs: action (required), scope, case_id, confirm, +8 more. Returns: case, note, plan, outcome, +2 more

manage_membersManage workspace membersA
Destructive
Inspect

Admin-only membership controls. list returns members and pending invites. invite adds/renews an email invite (default member; existing members refused); email_sent reports best-effort delivery. resend_invite renews by invite_id; revoke_invite withdraws. set_role never demotes the last admin. set_manager sets/clears a manager, rejecting self-reporting and cycles. set_read_scope (sees) and set_write_scope (edits/deletes) take own/team/all/null (role default), optionally include_reports; never admins. remove cannot target yourself or the last admin; records remain. Except list/revoke_invite, actions preview the person/change until confirm:true. This connection is bound to one membership; leave/switch your own workspace in the browser.

When to use: An admin manages membership, invitations or an individual's access.

Example: Invite sara@brightside.example as a manager.

Inputs: action (required), role, email, confirm, +6 more. Returns: note, action, invite, member, +5 more

manage_time_blocksManage time blocksA
DestructiveIdempotent
Inspect

Manage personal Google/Outlook calendar blocks with no attendees; nothing is sent. Uses booking_calendar_id (get_scheduling_settings), or Outlook's default calendar; busy unless show_as is free. create needs title, starts_at, ends_at (max 24h apart) and a fresh request_id UUID; reuse it only to retry the same block. reminder_minutes sets popup lead time; omit for calendar defaults, or use 0 on a short reminder block. list uses from/to (default next 14 days, max 62). busy returns the busy times on every calendar that blocks yours (from/to, default next 7 days, max 31; no titles), so a block can go in a free gap without the meeting card. update needs block_id and changed fields; starts_at alone preserves duration. remove deletes the block: first call asks, then requires confirm:true. Only Capable-created blocks can change.

When to use: Block focus time in a free gap, add reminders, or adjust your own blocks; use find_times for meetings with others.

Example: Block 9–11 tomorrow for writing.

Inputs: action (required), to, from, notes, +9 more. Returns: to, busy, from, note, +10 more

manage_webhooksManage change webhooksA
Destructive
Inspect

Admin-only change-feed webhooks. list shows status/last delivery. create starts signed JSON batches of read_changes metadata: object, record, verb and changed field names, never values; oldest first, after a minute. update patches URL, description or object_types (null=all). pause/resume stop/restart delivery; rotate_secret issues a new secret; test posts a ping now; delete removes the webhook. Creating, changing URL, rotating or deleting previews first and needs confirm:true. Failures retry with backoff, disabling after a day; list gives the reason and resume re-enables. Up to 10 per workspace; HTTPS public-host URLs only.

When to use: An admin connects another system to CRM changes without polling.

Example: Set up https://hooks.example.com/capable.

Inputs: action (required), url, confirm, webhook_id, +2 more. Returns: note, action, secret, applied, +5 more

merge_recordsMerge duplicate recordsA
Destructive
Inspect

Merge duplicate contacts/accounts. Contact blanks fill without overwrites; links move (activities/tasks/notes/deals/rosters/enrollments/meetings/attachments/relationship fields). Email/phone/LinkedIn identities stay with the survivor. The archived duplicate points to it, so its id still resolves. Colliding rows (same activity or active sequence enrollment) stay in duplicate history and appear in collisions. Account merges require a workspace admin and active Core workspace; Core billing rules apply, without field filling. Preview first; only confirm:true changes data. Without keep_id/merge_id, list possible duplicates with the older record proposed to keep; record_id narrows the list.

When to use: Two records represent one person/company: merge to preserve history instead of deleting the twin.

Example: Merge these duplicate people; keep the one linked to the company.

Inputs: object_type (required), limit, confirm, keep_id, +4 more. Returns: kept, note, filled, merged, +8 more

migrate_crmImport CRM exportsAInspect

Admin CRM import: describe → preview (no writes) → user reviews exact values/exclusions → stage the same preparation → start jobId in background. Explain preview.activationGuidance before starting; activation is reviewed separately and waiting rows remain saved for resume. Stage also returns guidance. Page status/list for every outcome. Identical source identity/payload is skipped; changed identities and email/domain collisions require manual resolution, never name merges. Resolve per-record approval requirements first: they block imports. Historical imports emit no automation events or enrichment. Custom objects, workflows, attachments and unavailable history need separate scoping. See inputs for authority, mappings, limits and retries. snake_case input aliases are accepted; outputs unchanged.

When to use: An administrator imports a Salesforce, HubSpot, Attio or CSV export with explicit mappings and resumable progress.

Example: Help me move our CRM data to Capable.

Inputs: action (required), name, files, jobId, +9 more. Returns: job, jobs, note, error, +4 more

propose_meetingPropose meetingAInspect

Place reversible, expiring, invitee-invisible calendar holds and STAGE the invitee email; this tool never emails anyone. First confirm topic AND agenda once with the user. Keep names out of the topic; address the invitee as you in the agenda. Pass exactly 3 slots verbatim from find_times or the card's confirmed picks; list deliberate busy picks in busy_override_starts. co_host_emails is workspace members only; invitees use invitee_email/additional_invitee_emails. Relay dropped_co_hosts. Search for known account/contact/opportunity IDs; never invent them. Returns full state, picker_url and staged_invite_preview. A clear human go on content is authorization to send: call send_meeting_invite in the same turn, not a separate approval gate. Withhold only if explicitly told to hold, or without invitee_email (share picker_url). Never send without a human go. Details: capable://guide/scheduling.

When to use: After the user chooses times and approves the content.

Example: Set up our agreed meeting.

Inputs: slots (required), topic (required), agenda (required), duration_min (required), +12 more. Returns: note, slots, meeting, guidance, +8 more

propose_updatesPropose updates
Read-only
Inspect

Use for requested CRM changes from notes, emails or freeform requests. Returns context, not a review. Assemble ALL records, people, links, activities and explicit tasks, then call review_proposed_updates without asking. Never save parents for IDs or call write tools directly; use create keys and {"$ref":"key"} object links. Ask once in app OR chat. Corrections replace the pending plan via replaces_receipt; after saving propose only NEW changes. Reuse matched_entities IDs/state/history; resolve entity_resolution ambiguities or missing facts with targeted reads before review. Never invent IDs. Stored work: pass source_touch_id; pinned:true links outrank heuristic matches. Pass source candidate_names for lowercase/uncased names.

When to use: After any meaningful conversation, email, or note about a relationship. Pass the text in text.

Example: Extract CRM changes from these call notes.

Inputs: text, transcript, source_type, candidate_names, +1 more. Returns: phase, guidance, workspace, next_action, +11 more

read_changesRead what changedA
Read-only
Inspect

The workspace's change feed, oldest first: each record created, updated, archived, restored or deleted on any object, with the names of the changed fields (never values), when, the actor and the basis of the values (person, reviewed, approved, collected, imported, automated). Fetch the records themselves with get_record. Pass next_cursor back as cursor; a first call starts at since (default the last 24 hours). A change appears a minute after it happened, so a cursor never skips one. 30 days are kept: a cursor older than oldest_cursor means read the records you track afresh, then continue.

When to use: An agent that keeps something in step with Capable, or needs to know what moved since it last looked, instead of polling searches or reports.

Example: What changed in the CRM since yesterday morning?

Inputs: limit, since, cursor, object_types. Returns: note, changes, has_more, next_cursor, +2 more

record_meetingRecord meetingA
Destructive
Inspect

Send the Capable notetaker bot to a video call. Pass meeting_url to start recording a call happening now, or match to find the rep's next upcoming calendar meeting by title/attendee and schedule the bot to join it. With neither, schedules the very next upcoming meeting that has a join link. The transcript auto-files onto the matching account/contact/opportunity when ready. The workspace admin must have Meeting recorder enabled; otherwise this refuses without scheduling or dispatching a bot.

When to use: Ad-hoc recording. Auto-record handles scheduled meetings on its own; use this to grab a live call by URL or book the user's next meeting with a specific customer.

Example: Record my next call with Acme.

Inputs: match, meeting_url. Returns: recording

remove_account_contactUnlink contact from accountA
Destructive
Inspect

Unlink a contact from an account (the contact and the account themselves are kept). Hard-deletes the M2M row — there's no historical value to preserving an ended role. DESTRUCTIVE: confirm with the user first, then call again with confirm: true.

When to use: When someone leaves the company or their role ends.

Example: Remove Mark from the Acme contact list — he's left the company.

Inputs: account_id (required), contact_id (required), confirm. Returns: note, removed, account_id, contact_id, +1 more

renew_subscriptionRenew subscriptionA
Destructive
Inspect

Renew a subscription: advance current_term_started_at and current_term_ends_at forward by one billing cadence (or accept explicit dates), optionally update mrr_cents/seats/plan_name (for renewals with uplift). Writes a subscription_events row of type 'renewed'. Link to the closed-won renewal opportunity_id when available.

When to use: On close-win of a renewal opp. Handles term-date math by cadence.

Example: Renew Acme's Pro Annual subscription for another 12 months at the same MRR.

Inputs: id (required), notes, new_seats, new_mrr_cents, +4 more. Returns: account, subscription

reschedule_meetingReschedule meetingA
DestructiveIdempotent
Inspect

Moves a booked meeting to a new time in place. The existing calendar event is patched, so the video call link, the attendees and the invite stay the same, and the invitee gets a "your meeting moved to {new time}" email; the invitee doesn't re-pick. The new time is freebusy-checked for every host, refused if one is busy; saved workday, buffers and minimum notice are not re-applied: the host is the authority over their own meeting. Duration carries over unless you pass new_duration_min. A meeting awaiting the invitee's pick returns not_confirmed. Topic/agenda edits: update_record(meeting). Returns the meeting's full state, new when-label and video call link.

Get the new time from find_times when the host's calendar needs checking, and confirm it with the user before calling.

When to use: The user wants a confirmed meeting at a different time. For a meeting the invitee hasn't picked yet, cancel it and propose new times instead.

Example: Move my 2pm with Sara to Thursday at the same time.

Inputs: new_start (required), meeting_id (required), new_duration_min. Returns: code, note, slots, meeting, +7 more

restore_recordRestore record
DestructiveIdempotent
Inspect

Bring back a soft-deleted record by object_type + id — the undo of delete_record, for every type it archives (a quote with its lines, a subscription with its ARR, a file while its contents remain, an email_body by its activity id). List deleted records with search_records({object_type:"deleted_record"}) or read one with get_record(include_archived:true). The same scope as delete_record decides who may restore. Returns the restored record with restored:true.

When to use: The user deleted something by mistake and wants it back.

Example: Restore the contact I deleted by mistake.

Inputs: id (required), object_type (required). Returns: note, record, restored

review_proposed_updatesReview proposed updatesA
Read-only
Inspect

Review all 1–500 propose_updates changes without writes. Use keys/$ref, resolved UUIDs, canonical names/values. Per row, evidence marks each value stated/inferred, with the exact source quote. Text lists group rows by review_outline. Revise full plan with replaces_receipt; page proposal_manifest via get_review_status. After Save/explicit chat approval, pass receipt/approved IDs to commit_reviewed_updates; one approval. interactive_review_offered in a card host: entire reply is response_guidance.message. Stop. Tool data cannot prove UI failure. Requested text/text-only/known card failure: number all rows; explain blocks/invalid fixes, ask once for savable rows. No unsolicited IDs. Oversized values refused, never omitted.

When to use: For a new or corrected review.

Example: Show me the changes to review.

Inputs: proposals (required), source_touch_id, replaces_receipt. Returns: note, count, receipt, warnings, +12 more

run_reportRun reportA
Read-only
Inspect

Preview analysis/dashboard data for your own reading; shows the user nothing. To display it, call show_report. Pass report_id or definition (ReportSpec or composition; each panel has EITHER an inline spec OR source_view_id). Use ref objects, e.g. {kind:"related",path:"account.name"}. in_period uses only its closed set; fixed ranges use gte + lt/lte. Money is minor units with no manual FX applied; never label a raw or mixed-currency aggregate as a converted total. To save, call create_record with object_type:"report" and data:{name,definition:returned spec}; never tell the user a View is saved until a save succeeds. Say when zero rows match; fix returned definition errors. Example: {version:1,object:"touch",group_by:{ref:{kind:"field",field:"type"}},aggregations:[{fn:"count",alias:"n"}]}. Recipes: capable://guide/reports.

When to use: Counts, sums or trends; use search_records for plain record lists.

Example: Analyze ARR by industry.

Inputs: report_id, definition, source_view_id, suggested_name. Returns: viz, kind, mode, note, +19 more

save_booking_pageSave booking pageA
DestructiveIdempotent
Inspect

Create a private booking-page draft or edit one of your pages. Creation requires topic and a new request_id UUID; reuse the exact UUID and details on retry. Defaults: 30 minutes, 14 days, empty description. To edit, pass page_id and its expected_updated_at; only supplied fields change. Edits preserve the URL and publication state. This never publishes a draft or sends messages. Use set_booking_page_status when the user asks to publish.

When to use: Create a private draft or patch one of your pages. Reuse the creation request_id on retries; editing needs the page's current version. Publishing is a separate requested action.

Example: Create a draft 30-minute intro page with a two-week booking window.

Inputs: topic, page_id, video_url, request_id, +4 more. Returns: note, page, updated

schedule_reportSchedule reportA
DestructiveIdempotent
Inspect

Schedule one saved analysis to be emailed as a digest (CSV attached) to workspace members on a daily / weekly / monthly cadence (UTC); a dashboard cannot be scheduled — choose or save one panel as an analysis first. One schedule per report: calling again replaces every field, so re-pass conditions and recipients to keep them. day_of_week (0=Sun) applies weekly, day_of_month (1–28) monthly; recipients default to you. With conditions the digest sends only when ANY is met by that run's result, else that occurrence is skipped. Returns the schedule. List schedules with search_records(report_schedule); delete one with delete_record(report_schedule).

When to use: The user wants a saved analysis emailed on a schedule — 'email me this every Monday'.

Example: Email the pipeline report to the sales team every Monday at 8am.

Inputs: frequency (required), report_id (required), hour, enabled, +4 more. Returns: schedule

search_recordsSearch recordsA
Read-only
Inspect

List/filter any object; built-ins use typed search filters. Returns records, count, object_type, next_cursor, has_more and search_coverage. Follow every page for exhaustive answers. Unsupported filters are ignored and echoed in ignored_filters with coverage status unsupported_query: these rows do not answer the question; fix inputs before claiming matches or none. Unknown types return valid types. Most objects sort newest first; tasks by due ascending, undated last. Opportunity rows include account_last_inbound_at/account_last_touch_at for reply-recency questions. Task projection:'actions' includes sequence steps, deduplicates reminders, and returns exact counts plus paged rows. Write using taskId/enrollmentId, never projection ids. Nothing is sent.

When to use: A plain list — open tasks, deals in a stage, contacts at an account — before run_report; email matches carry a highlighted snippet.

Example: Find the emails to sally@acme.com.

Inputs: object_type (required), limit, query, cursor, +2 more. Returns: note, count, total, counts, +10 more

send_meeting_inviteSend meeting inviteA
DestructiveIdempotent
Inspect

Sends the picker email to the invitee. Idempotent: an already-sent invite never re-sends. Errors when the meeting isn't awaiting the invitee's pick, or when it was created in shareable mode (no invitee email; share the picker_url instead). A workspace governance policy may still require_approval on this tool; that path is independent. Returns the meeting's full state.

When to use: In the same turn as propose_meeting, once the user has okayed the topic and agenda: that content go-ahead is the authorization to send, so don't ask for a separate send confirmation. On its own only when the user earlier said to hold the send and is now telling you to send it. Never without a clear human go, never on your own initiative.

Example: Okay, send Sara that invite now.

Inputs: meeting_id (required). Returns: sent, slots, meeting, picker_url, +2 more

set_booking_page_statusPublish or pause booking pageA
DestructiveIdempotent
Inspect

Publish or pause your booking page when the user requests it. Publishing makes the URL accept bookings from anyone with the link, after checking timezone and calendar readiness. Pausing prevents new bookings; existing meetings and guest links keep working. Read the page's current version first. Nothing is sent. To delete a page: delete_record(booking_page).

When to use: Publish or pause your page when asked, using its current version. Publishing checks readiness; pausing keeps its URL and existing meetings.

Example: Publish my intro booking page and give me its link.

Inputs: page_id (required), published (required), expected_updated_at (required). Returns: note, page, updated

set_exchange_ratesSet exchange ratesA
DestructiveIdempotent
Inspect

Set/remove Fixed workspace FX rates (admin-only). Fixed overrides the daily ECB Automatic reference rate until changed; removing restores Automatic. Direction: 1 input-currency unit = rate in default currency (DKK default: {currency:"EUR",rate:7.46} means 1 EUR = 7.46 DKK). Reversed-looking rates or rates outside 0.8–1.25× the bank rate require confirm:true; without it nothing saves, and the response supplies the question/reference/suggested correction. Upserts and removals are atomic; ambiguous requests change nothing. Stored amounts never change; totals convert only if every currency has a rate. Returns default currency, Fixed rates, bank date and effective rates.

When to use: An admin chooses a budget/contract rate or returns a currency to Automatic.

Example: Fix 1 EUR at 7.46 DKK; reset USD.

Inputs: remove, upsert, confirm. Returns: rates, updated, workspace, bank_rates, +12 more

set_opportunity_productsSet opportunity productsA
DestructiveIdempotent
Inspect

Replace an opportunity's entire product set and derive its value. Pass catalog product IDs/quantities, never prices; [] clears all lines and sets value to zero. The server snapshots unit_price_cents and computes totals: per_unit multiplies by quantity, flat charges once (quantity >1 is flagged). Discounts are percentages via line/top-level discount_pct; the server computes money. Bundles expand automatically; out-of-tier quantities are flagged, not blocked. include_discontinued:true allows a discontinued item on an existing agreement. Returns the fresh opportunity, priced lines and flags.

When to use: Price a deal from selected products after applying the opportunity_products template.

Example: Put 15 standard-plan units on Acme’s deal.

Inputs: lines (required), opportunity_id (required), discount_pct. Returns: note, updated, guidance, line_items, +4 more

share_recordingShare a call recordingInspect

Share one recorded call outside the workspace through a private, expiring link to a page that plays it and, unless include_transcript is false, its transcript. create (default): emails each recipient their own link as "{you} via Capable" (replies reach you), or with no recipients returns one link to send yourself; a link is shown once. Needs confirm:true — without it, a preview and nothing sent. list: the links with status and plays, plus the call's outside attendees as suggested_recipients. revoke: turn one link off by share_id.

When to use: When someone outside the workspace asks for a call's recording — email them a private, expiring link, or get one to send yourself; list or revoke links later.

Example: Send Anna the recording of yesterday's call with Acme.

Inputs: recording_id (required), action, confirm, message, +4 more. Returns: note, share, action, shares, +6 more

show_reportShow reportA
Read-only
Inspect

Show an analysis/dashboard from saved CRM records as a card with "Save as view", or text if unavailable/requested. report_id runs a saved report definition; definition runs an inline ReportSpec/composition. Resolve named subjects in their own object and include exact supported filters (company name/domain); a title never scopes data. For an attached report, give one line without repeating rows. Own reading: run_report. Showing saves nothing. Save only when asked via create_record with object_type:"report", data:{name,definition:returned spec}. Never tell the user a View is saved before success. Revisions pass source_view_id to update the existing View. Say when zero rows match. Money is minor units, not automatically converted totals. Shape: capable://guide/reports.

When to use: The user asks to see, chart or keep an analysis.

Example: Show ARR by industry.

Inputs: report_id, definition, source_view_id, suggested_name. Returns: viz, kind, mode, note, +11 more

show_workspace_setupShow workspace setupA
Read-only
Inspect

Show the workspace-setup step so the user can confirm the motion(s) you recommended, name the workspace, and save, in a card where the host shows one. The result carries the state and motions for a text reply. Commits via finalize_workspace_setup.

When to use: Only after you have welcomed the user, explained what a motion is, and shared your evidence-based read.

Example: Show me my setup options to confirm.

Inputs: suggested_motions. Returns: state, can_edit, guidance, checklist, +4 more

start_onboardingStart useful customer workB
Read-only
Inspect

Read saved choices, entry context and workspace evidence for one useful customer result. preferences saves explicit personal choices, never collection or write authority. Reuse accessible data and the team's setup. A useful brief or draft needs no CRM write. Setup is optional; admins confirm via finalize_workspace_setup. Only explicit collection consent permits start_import:true; then read again. Blank and CSV choices do not authorize email collection.

When to use: Start or resume useful customer work. Setup remains optional.

Example: Start Capable

Inputs: sources, preferences, start_import, source_provider. Returns: state, guidance, checklist, user_journey, +9 more

stop_recordingStop recordingA
Destructive
Inspect

Pull the notetaker bot out of a call and cancel the recording. Use when a rep asks not to record a meeting the bot was scheduled for, or to remove it mid-call.

When to use: When a rep doesn't want a scheduled meeting recorded, or wants the bot removed mid-call.

Example: Don't record my 3pm — pull the bot off it.

Inputs: recording_id (required). Returns: recording

update_availabilityUpdate saved availabilityA
DestructiveIdempotent
Inspect

Patch personal availability/photo across workspaces; existing meetings stay put. Arrays replace: preserve unrequested entries. Hours use the saved IANA timezone. One-off constraints use find_times. enable_scheduling:true alone activates Google scheduling after consent, without publishing a page. Save other edits separately.

When to use: After reading settings: change personal availability, your recording notice or catch-up, or explicitly enable scheduling.

Example: Keep my current schedule, but leave 15 minutes after each meeting.

Inputs: expected_updated_at (required), catch_up, timezone, workdays, +10 more. Returns: note, updated, catch_up, availability, +3 more

update_objectUpdate object typeA
DestructiveIdempotent
Inspect

Admin-only patch of a custom object's label, plural, blurb, icon, shared-write mode, enabled flag or display_field (null resets to name). show_in_menu changes navigation only; hiding a menu row leaves the object usable. Built-in keys accept only enabled and show_in_menu. enabled:false hides records across the workspace and makes generic verbs refuse the object until re-enabled; nothing is deleted. Preview first, then confirm:true to disable; enabling needs no confirmation. describe_schema.switchable identifies objects that allow switching; foundational objects and feature parts do not. Returns the definition, or key and changes for a built-in/menu-only update.

When to use: An admin reconfigures an object type or its menu visibility.

Example: Rename the Property object to Listing.

Inputs: key (required), icon, blurb, label, +6 more. Returns: key, note, label, object, +3 more

update_pipelineUpdate pipelineA
DestructiveIdempotent
Inspect

Update a pipeline by pipeline_key (or pipeline_id; id wins): rename it (label), re-point it (applies_to), replace its stages (including each stage's entry requirements) or set which opportunity types default to it (default_for_types). Existing stage keys stay stable; a stage with open deals can't be removed (reassign them first). Omit both key and id to reshape the WORKSPACE DEFAULT pipeline — only stages apply there. An unknown key or id returns the known pipelines instead of an error. Admin-only. Returns the updated pipeline.

When to use: When an admin wants to rename a pipeline, change its stages or their entry requirements, re-point it, or set which deal types default onto it; omit the pipeline key to reshape the workspace default pipeline's stages.

Example: Don't let a deal reach Proposal until Metrics and an economic buyer are filled in.

Inputs: label, stages, applies_to, pipeline_id, +2 more. Returns: pipeline

update_quoteUpdate quoteA
DestructiveIdempotent
Inspect

Update a quote: change its status (exactly draft → sent → accepted / lost), link an opportunity, or replace its line items. When you pass lines, the SERVER re-prices from the catalog and replaces the whole line set, recomputing the total — you never pass a price (catalog products price from unit_price_cents (integer cents) and pricing_mode on the product object; per_unit multiplies by quantity, flat charges once, a missing or unknown pricing_mode resolves to flat, a flat line with quantity > 1 is flagged). Discounts are percent only (per-line discount_pct and/or a quote-level discount_pct) and apply when you re-price, so pass lines to change a discount. Status- or opportunity-only edits don't re-price. A quote is a pre-commit artifact (invoicing and contracts happen elsewhere). Returns the updated quote, its priced lines and flags.

When to use: The user wants to change a quote that already exists.

Example: Mark Acme's quote as sent, and add 5 more units.

Inputs: id (required), name, lines, notes, +4 more. Returns: note, quote, updated, guidance, +7 more

update_recordUpdate record
DestructiveIdempotent
Inspect

Patch object_type + id; returns the fresh record. Built-ins use typed domain logic; custom data is shallow-merged. Update an existing View with report + patch:{definition}; create a View only for a different perspective. Activity patches correct subject/summary/time/type. Sequence plans save together with saved step ids, revisions and an identical-retry request_id; enrollment fences timing/channel/order changes. Maintenance fields each run alone: task subtasks replaces the checklist; contact engaged:true is a ratchet; opportunity board_rank orders its column; sequence_step position swaps neighbours, fenced while people are partway through. See patch for syntax; task due follows create_record.

When to use: Edit fields (stage, task status:'done'). Retire converted leads LAST: status:'converted', account/contact/opportunity ids, converted_at, deleted_at; see an MCP resource at capable://guide/leads.

Example: Update opportunity : set stage to verbal.

Inputs: id (required), patch (required), object_type (required), expected_revision. Returns: note, record, result, updated, +2 more

update_scheduling_calendarsUpdate scheduling calendarsA
DestructiveIdempotent
Inspect

Choose which of your connected calendars block availability and where new meetings are created. Read get_scheduling_settings for calendar IDs and the current version. Omitted fields stay unchanged; conflict_calendar_ids replaces the full list. The destination must be writable and is always included in conflict checks. Existing meetings stay on their original calendars. Does not connect accounts or grant permissions.

When to use: Choose which connected calendars block your time and which writable calendar receives bookings. Read current IDs and the version first; selections apply across your workspaces.

Example: Check both my work and personal calendars, and put bookings on my work calendar.

Inputs: expected_updated_at (required), booking_calendar_id, conflict_calendar_ids. Returns: note, updated, calendars

update_workspaceUpdate workspace settingsA
DestructiveIdempotent
Inspect

Admin PATCH; omitted/unchanged fields stay. Name/framework: finalize_workspace_setup. Recorder/notice/domain-join switches, read_scope_by_role, write_scope_by_role and autonomy_by_role (manage_approvals action:"autonomy" shows the evidence) need confirm:true; otherwise preview. lead_notifications (send alone): read returns rule/version, members, fields, status; configure uses expected_version (null if absent) and confirm:true. source_filter:null matches all new leads, else exact match. Recipients: owner, members (max20 IDs), or inbox (recipient_email). Empty IDs except members; null email except inbox. message_field_key:null omits message. Internal, default off, no backfill. /developers#website-enquiries. health_rules (send alone): customer health rules; a rule never sets health_state.

When to use: An admin changes workspace preferences, access, automation, internal lead alerts or the customer health rules.

Example: Set our timezone to Europe/Stockholm.

Inputs: flags, confirm, logo_url, timezone, +16 more. Returns: note, changed, changes, updated, +5 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP-native CRM backend for AI agents, enabling customer, opportunity, note, follow-up, and pipeline health management through 15 MCP tools.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      CRM AI - MCP server providing AI-powered tools and automation by MEOK AI Labs
      3 npm
      54 PyPI
      MIT
    • F
      license
      B
      quality
      C
      maintenance
      Enables managing a small CRM of companies, contacts, deals, and activities through MCP tools, including creating and updating records, logging activities, searching across the CRM, and summarizing pipeline stages.
      15
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to read and write CRM data—companies, contacts, opportunities, tasks, and interactions—through MCP, with OAuth and provenance tracking for every value.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources