@chronary/toolkit 1.7.0 → 1.7.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.cjs CHANGED
@@ -1152,14 +1152,14 @@ var RAW_TOOL_DEFINITIONS = [
1152
1152
  },
1153
1153
  {
1154
1154
  name: "update_agent",
1155
- description: "Update an agent's name, description, metadata, or status (active/paused). Requires an Organization key \u2014 Agent keys cannot mutate agents.",
1155
+ description: "Update an agent's name, description, metadata, or status (active/paused). Setting status on a decommissioned agent restores it and makes its calendars writable again; that is refused with quota_exceeded when the agent, its calendars or their recurring series would put the organization over the plan's agent, calendar or recurring series limit. Requires an Organization key \u2014 Agent keys cannot mutate agents.",
1156
1156
  schema: UpdateAgentSchema,
1157
1157
  annotations: { title: "Update Agent", readOnlyHint: false, destructiveHint: false, idempotentHint: true, openWorldHint: false },
1158
1158
  execute: createExecutor(updateAgent)
1159
1159
  },
1160
1160
  {
1161
1161
  name: "delete_agent",
1162
- description: "Decommission an agent. This marks the agent as decommissioned and revokes all of its Agent keys. Requires an Organization key \u2014 Agent keys cannot delete agents.",
1162
+ description: "Decommission an agent. This marks the agent as decommissioned and revokes all of its Agent keys. Its calendars and events are kept but stop counting toward the plan's calendar limit, and they are read-only (writes return agent_inactive) until the agent is restored with update_agent. Requires an Organization key \u2014 Agent keys cannot delete agents.",
1163
1163
  schema: DeleteAgentSchema,
1164
1164
  annotations: { title: "Delete Agent", readOnlyHint: false, destructiveHint: true, idempotentHint: true, openWorldHint: false },
1165
1165
  execute: createExecutor(deleteAgent)
@@ -1212,7 +1212,7 @@ var RAW_TOOL_DEFINITIONS = [
1212
1212
  // ── Scheduling proposals ───────────────────────────────────────
1213
1213
  {
1214
1214
  name: "create_proposal",
1215
- description: "Create a scheduling proposal \u2014 send a set of candidate time slots to one or more participant agents so they can accept, decline, or counter-propose. The organizer agent owns the proposal; once every participant responds, the system auto-resolves to the highest-scoring slot (or cancels if all decline). Requires an Organization key. Pro plan only.",
1215
+ description: "Create a scheduling proposal \u2014 send a set of candidate time slots to one or more participant agents so they can accept, decline, or counter-propose. The organizer agent owns the proposal; once every participant responds, the system auto-resolves to the highest-scoring slot (or cancels if all decline). Requires an Organization key and a Developer or Pro plan.",
1216
1216
  schema: CreateProposalSchema,
1217
1217
  annotations: { title: "Create Proposal", readOnlyHint: false, destructiveHint: false, idempotentHint: false, openWorldHint: false },
1218
1218
  execute: createExecutor(createProposal)
@@ -1233,21 +1233,21 @@ var RAW_TOOL_DEFINITIONS = [
1233
1233
  },
1234
1234
  {
1235
1235
  name: "respond_to_proposal",
1236
- description: 'Submit a response (accept / decline / counter) on behalf of one participant agent to an open proposal. An "accept" requires the slot id from the proposal; a "counter" can suggest alternative slots. When all participants have responded the proposal auto-resolves \u2014 no separate resolve call needed in the normal flow. Requires an Organization key. Pro plan only.',
1236
+ description: 'Submit a response (accept / decline / counter) on behalf of one participant agent to an open proposal. An "accept" requires the slot id from the proposal; a "counter" can suggest alternative slots. When all participants have responded the proposal auto-resolves \u2014 no separate resolve call needed in the normal flow. Requires an Organization key and a Developer or Pro plan.',
1237
1237
  schema: RespondToProposalSchema,
1238
1238
  annotations: { title: "Respond To Proposal", readOnlyHint: false, destructiveHint: false, idempotentHint: false, openWorldHint: false },
1239
1239
  execute: createExecutor(respondToProposal)
1240
1240
  },
1241
1241
  {
1242
1242
  name: "resolve_proposal",
1243
- description: 'Force-resolve an open proposal using responses collected so far. Picks the highest-scoring slot among those accepted by the most participants and creates a confirmed calendar event. If every response was "decline", the proposal is cancelled instead. Use when you want to close out a proposal without waiting for every participant. Requires an Organization key. Pro plan only.',
1243
+ description: 'Force-resolve an open proposal using responses collected so far. Picks the highest-scoring slot among those accepted by the most participants and creates a confirmed calendar event. If every response was "decline", the proposal is cancelled instead. Use when you want to close out a proposal without waiting for every participant. Requires an Organization key and a Developer or Pro plan.',
1244
1244
  schema: ResolveProposalSchema,
1245
1245
  annotations: { title: "Resolve Proposal", readOnlyHint: false, destructiveHint: false, idempotentHint: true, openWorldHint: false },
1246
1246
  execute: createExecutor(resolveProposal)
1247
1247
  },
1248
1248
  {
1249
1249
  name: "cancel_proposal",
1250
- description: 'Cancel an open proposal. Fires a proposal.cancelled webhook with reason="organizer_cancelled". Requires an Organization key. Pro plan only.',
1250
+ description: 'Cancel an open proposal. Fires a proposal.cancelled webhook with reason="organizer_cancelled". Requires an Organization key. Works on every plan, so an org that dropped to Free can still cancel proposals it made on a paid plan.',
1251
1251
  schema: CancelProposalSchema,
1252
1252
  annotations: { title: "Cancel Proposal", readOnlyHint: false, destructiveHint: true, idempotentHint: true, openWorldHint: false },
1253
1253
  execute: createExecutor(cancelProposal)
@@ -1460,7 +1460,7 @@ var RAW_TOOL_DEFINITIONS = [
1460
1460
  },
1461
1461
  {
1462
1462
  name: "request_upgrade",
1463
- description: "Ask your human to upgrade this Chronary account to Pro. Returns approval_url \u2014 give it to your human; only a human can pay. If reused=true a request is already pending \u2014 do not call again; poll get_upgrade_request at most once a minute. The link opens the Billing page in the Chronary console.",
1463
+ description: "Ask your human to upgrade this Chronary account to the next plan up (Free to Developer, Developer to Pro). Returns approval_url \u2014 give it to your human; only a human can pay. If reused=true a request is already pending \u2014 do not call again; poll get_upgrade_request at most once a minute. The link opens the Billing page in the Chronary console.",
1464
1464
  schema: RequestUpgradeSchema,
1465
1465
  annotations: { title: "Request Upgrade", readOnlyHint: false, destructiveHint: false, idempotentHint: true, openWorldHint: false },
1466
1466
  execute: createExecutor(requestUpgrade)
@@ -1496,7 +1496,7 @@ Typical flow: create_agent -> create_calendar -> create_event / get_availability
1496
1496
 
1497
1497
  When checking availability, always inspect availability_state and warnings before treating returned slots as complete. Human-calendar setup requires a human to open setup_url and consent; agents never receive provider credentials or calendar contents.
1498
1498
 
1499
- Organization keys (chr_sk_) can use every tool; Agent keys (chr_ak_) are limited to their own agent and cannot use org-only tools such as create_agent or find_meeting_time. Scoped keys, cross-agent availability, webhook delivery replay and secret rotation require a Developer or Pro plan; scheduling proposals and temporal holds require Pro.
1499
+ Organization keys (chr_sk_) can use every tool; Agent keys (chr_ak_) are limited to their own agent and cannot use org-only tools such as create_agent or find_meeting_time. Scoped keys, cross-agent availability, scheduling proposals, temporal holds, webhook delivery replay and secret rotation require a Developer or Pro plan.
1500
1500
 
1501
1501
  If you hit a plan limit, don't retry in a loop: call get_billing, then request_upgrade, and give approval_url to your human. Agents cannot pay; a human completes checkout.
1502
1502