@chronary/toolkit 1.7.0 → 1.7.1

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.d.cts CHANGED
@@ -1,6 +1,6 @@
1
1
  import { ZodRawShape } from 'zod';
2
2
  import { ListToolkit, ToolAnnotations, ChronaryToolkitConfig, ToolDefinition } from './index.cjs';
3
- export { M as MCP_SERVER_INSTRUCTIONS } from './instructions-CQAfBjV3.cjs';
3
+ export { M as MCP_SERVER_INSTRUCTIONS } from './instructions-BJQzbMAM.cjs';
4
4
  import '@chronary/sdk';
5
5
 
6
6
  interface McpToolDefinition {
package/dist/mcp.d.ts CHANGED
@@ -1,6 +1,6 @@
1
1
  import { ZodRawShape } from 'zod';
2
2
  import { ListToolkit, ToolAnnotations, ChronaryToolkitConfig, ToolDefinition } from './index.js';
3
- export { M as MCP_SERVER_INSTRUCTIONS } from './instructions-CQAfBjV3.js';
3
+ export { M as MCP_SERVER_INSTRUCTIONS } from './instructions-BJQzbMAM.js';
4
4
  import '@chronary/sdk';
5
5
 
6
6
  interface McpToolDefinition {
package/dist/mcp.js CHANGED
@@ -1045,7 +1045,7 @@ var RAW_TOOL_DEFINITIONS = [
1045
1045
  // ── Scheduling proposals ───────────────────────────────────────
1046
1046
  {
1047
1047
  name: "create_proposal",
1048
- 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.",
1048
+ 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.",
1049
1049
  schema: CreateProposalSchema,
1050
1050
  annotations: { title: "Create Proposal", readOnlyHint: false, destructiveHint: false, idempotentHint: false, openWorldHint: false },
1051
1051
  execute: createExecutor(createProposal)
@@ -1066,21 +1066,21 @@ var RAW_TOOL_DEFINITIONS = [
1066
1066
  },
1067
1067
  {
1068
1068
  name: "respond_to_proposal",
1069
- 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.',
1069
+ 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.',
1070
1070
  schema: RespondToProposalSchema,
1071
1071
  annotations: { title: "Respond To Proposal", readOnlyHint: false, destructiveHint: false, idempotentHint: false, openWorldHint: false },
1072
1072
  execute: createExecutor(respondToProposal)
1073
1073
  },
1074
1074
  {
1075
1075
  name: "resolve_proposal",
1076
- 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.',
1076
+ 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.',
1077
1077
  schema: ResolveProposalSchema,
1078
1078
  annotations: { title: "Resolve Proposal", readOnlyHint: false, destructiveHint: false, idempotentHint: true, openWorldHint: false },
1079
1079
  execute: createExecutor(resolveProposal)
1080
1080
  },
1081
1081
  {
1082
1082
  name: "cancel_proposal",
1083
- description: 'Cancel an open proposal. Fires a proposal.cancelled webhook with reason="organizer_cancelled". Requires an Organization key. Pro plan only.',
1083
+ 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.',
1084
1084
  schema: CancelProposalSchema,
1085
1085
  annotations: { title: "Cancel Proposal", readOnlyHint: false, destructiveHint: true, idempotentHint: true, openWorldHint: false },
1086
1086
  execute: createExecutor(cancelProposal)
@@ -1349,7 +1349,7 @@ Typical flow: create_agent -> create_calendar -> create_event / get_availability
1349
1349
 
1350
1350
  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.
1351
1351
 
1352
- 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.
1352
+ 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.
1353
1353
 
1354
1354
  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.
1355
1355
 
@@ -1372,8 +1372,8 @@ iCal feeds, and receive webhooks.
1372
1372
  Organization keys (\`chr_sk_\`) can use every tool; Agent keys (\`chr_ak_\`) are
1373
1373
  limited to their own agent and cannot use org-only tools such as
1374
1374
  \`create_agent\` or \`find_meeting_time\`. Scoped keys, cross-agent availability,
1375
- webhook delivery replay and secret rotation require a Developer or Pro plan;
1376
- scheduling proposals and temporal holds require Pro.`;
1375
+ scheduling proposals, temporal holds, webhook delivery replay and secret
1376
+ rotation require a Developer or Pro plan.`;
1377
1377
  var ChronaryToolkit = class extends ListToolkit {
1378
1378
  constructor(config) {
1379
1379
  super(config);