@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/mcp.cjs CHANGED
@@ -1010,14 +1010,14 @@ var RAW_TOOL_DEFINITIONS = [
1010
1010
  },
1011
1011
  {
1012
1012
  name: "update_agent",
1013
- description: "Update an agent's name, description, metadata, or status (active/paused). Requires an Organization key \u2014 Agent keys cannot mutate agents.",
1013
+ 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.",
1014
1014
  schema: UpdateAgentSchema,
1015
1015
  annotations: { title: "Update Agent", readOnlyHint: false, destructiveHint: false, idempotentHint: true, openWorldHint: false },
1016
1016
  execute: createExecutor(updateAgent)
1017
1017
  },
1018
1018
  {
1019
1019
  name: "delete_agent",
1020
- 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.",
1020
+ 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.",
1021
1021
  schema: DeleteAgentSchema,
1022
1022
  annotations: { title: "Delete Agent", readOnlyHint: false, destructiveHint: true, idempotentHint: true, openWorldHint: false },
1023
1023
  execute: createExecutor(deleteAgent)
@@ -1070,7 +1070,7 @@ var RAW_TOOL_DEFINITIONS = [
1070
1070
  // ── Scheduling proposals ───────────────────────────────────────
1071
1071
  {
1072
1072
  name: "create_proposal",
1073
- 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.",
1073
+ 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.",
1074
1074
  schema: CreateProposalSchema,
1075
1075
  annotations: { title: "Create Proposal", readOnlyHint: false, destructiveHint: false, idempotentHint: false, openWorldHint: false },
1076
1076
  execute: createExecutor(createProposal)
@@ -1091,21 +1091,21 @@ var RAW_TOOL_DEFINITIONS = [
1091
1091
  },
1092
1092
  {
1093
1093
  name: "respond_to_proposal",
1094
- 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.',
1094
+ 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.',
1095
1095
  schema: RespondToProposalSchema,
1096
1096
  annotations: { title: "Respond To Proposal", readOnlyHint: false, destructiveHint: false, idempotentHint: false, openWorldHint: false },
1097
1097
  execute: createExecutor(respondToProposal)
1098
1098
  },
1099
1099
  {
1100
1100
  name: "resolve_proposal",
1101
- 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.',
1101
+ 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.',
1102
1102
  schema: ResolveProposalSchema,
1103
1103
  annotations: { title: "Resolve Proposal", readOnlyHint: false, destructiveHint: false, idempotentHint: true, openWorldHint: false },
1104
1104
  execute: createExecutor(resolveProposal)
1105
1105
  },
1106
1106
  {
1107
1107
  name: "cancel_proposal",
1108
- description: 'Cancel an open proposal. Fires a proposal.cancelled webhook with reason="organizer_cancelled". Requires an Organization key. Pro plan only.',
1108
+ 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.',
1109
1109
  schema: CancelProposalSchema,
1110
1110
  annotations: { title: "Cancel Proposal", readOnlyHint: false, destructiveHint: true, idempotentHint: true, openWorldHint: false },
1111
1111
  execute: createExecutor(cancelProposal)
@@ -1318,7 +1318,7 @@ var RAW_TOOL_DEFINITIONS = [
1318
1318
  },
1319
1319
  {
1320
1320
  name: "request_upgrade",
1321
- 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.",
1321
+ 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.",
1322
1322
  schema: RequestUpgradeSchema,
1323
1323
  annotations: { title: "Request Upgrade", readOnlyHint: false, destructiveHint: false, idempotentHint: true, openWorldHint: false },
1324
1324
  execute: createExecutor(requestUpgrade)
@@ -1374,7 +1374,7 @@ Typical flow: create_agent -> create_calendar -> create_event / get_availability
1374
1374
 
1375
1375
  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.
1376
1376
 
1377
- 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.
1377
+ 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.
1378
1378
 
1379
1379
  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.
1380
1380
 
@@ -1397,8 +1397,8 @@ iCal feeds, and receive webhooks.
1397
1397
  Organization keys (\`chr_sk_\`) can use every tool; Agent keys (\`chr_ak_\`) are
1398
1398
  limited to their own agent and cannot use org-only tools such as
1399
1399
  \`create_agent\` or \`find_meeting_time\`. Scoped keys, cross-agent availability,
1400
- webhook delivery replay and secret rotation require a Developer or Pro plan;
1401
- scheduling proposals and temporal holds require Pro.`;
1400
+ scheduling proposals, temporal holds, webhook delivery replay and secret
1401
+ rotation require a Developer or Pro plan.`;
1402
1402
  var ChronaryToolkit = class extends ListToolkit {
1403
1403
  constructor(config) {
1404
1404
  super(config);
@@ -1528,7 +1528,7 @@ var ChronaryToolkit = class extends ListToolkit {
1528
1528
  role: "user",
1529
1529
  content: {
1530
1530
  type: "text",
1531
- text: `Create a scheduling proposal "${title}" organized by ${organizer_agent_id} for participants ${participant_agent_ids}. First use get_availability / find_meeting_time to pick 2-3 candidate slots, then call create_proposal with those slots. Report the proposal ID. (Scheduling proposals require a Pro plan and an Organization key.)`
1531
+ text: `Create a scheduling proposal "${title}" organized by ${organizer_agent_id} for participants ${participant_agent_ids}. First use get_availability / find_meeting_time to pick 2-3 candidate slots, then call create_proposal with those slots. Report the proposal ID. (Scheduling proposals require a Developer or Pro plan and an Organization key.)`
1532
1532
  }
1533
1533
  }
1534
1534
  ]