Skip to main content
Glama

Propose an automation

propose_automation
Destructive

AI Agents: Use when the person wants something to keep happening by itself in one system, such as "when a deal is won, add a kick-off task". Writes one rule (when, only if, then) on one record type and returns it as a sentence, what it would have done in the last 30 days and an approval link; nothing runs yet. After their yes, call set_automation_status with approve; a rule that sends something is only switched on through the link. Field keys come from describe_record_type. Not for a one-off change (use a propose_ tool) or for syncing two systems (use plan_integration).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "system": "<system>",
      "name": "<name>",
      "type": "<type>",
      "trigger": "<trigger>",
      "actions": "<actions>"
    },
    "name": "propose_automation"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesA short name for the rule.
typeYesThe record type, such as contact or invoice.
systemYesThe AI agent: its system or connection name.
actionsYesThen: the actions, in order.
triggerYesWhen the rule acts.
replacesNoOptional id of an automation this rule replaces once approved.
conditionsNoOnly if: conditions that must all hold.
apply_to_existingNoAlso act once on records that already match.

Output Schema

NameRequiredDescriptionDefault
idYes
nameYes
ruleYes
typeYes
noticeNo
statusYes
examplesYes
sentenceYes
systemIdYes
warningsYes
lastRunAtYes
approveUrlYes
systemNameYes
pauseReasonYes
firings30DaysYes
matchedLast30DaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed22 schema fields changed
    • changedInput schema / properties / actions / description
      Previous value: -"Then: 1 to 3 actions, run in this order on the record that met the rule."New value: +"Then: the actions, in order."
    • changedInput schema / properties / actions / items / properties / arguments / description
      Previous value: -"For a change action: one item of that action's propose_ tool, for the record that met the rule. Use {record.id} as its id and leave type out for the rule's own record type. To act on the contact of a record, give type contact with {record.contact} as its id; on its deal, type opportunity with {record.deal}; on its job, {record.job}. To act on what an earlier action of the rule made (create_record, convert_estimate, convert_lead), use {action1.id} for the first action. To give a task or record to the owner of the record that met the rule, use {record.owner} as its user. For assign_owner, users is a list of user ids that take turns, one per record. For notify: to is owners or the emails of members of the CRM Connector account (at most 5), text what to tell (at most 900 characters) and optionally subject; it tells at most 50 times a day. A date may be {today} or {today+3} (three days after the rule acts). {record.field:Amount} is the value a field of the record that fired holds when the rule acts. For email_contact: subject, body, sender_name (the From name shown, 2 to 60 characters) and reply_to (the address replies go to), both required. The subject and body may use {contact.first_name}, {contact.name}, {record.name}, {organisation}; the address it goes to is always the contact's own."New value: +"For a propose_ action: one item of that tool with {record.id} as its id; {record.contact}, {record.deal}, {record.job}, {record.owner} and {action1.id} name other records. notify: to, text, subject. email_contact: subject, body, sender_name and reply_to; ask the person for the last two."
    • changedInput schema / properties / actions / items / properties / kind / description
      Previous value: -"The action the rule applies by itself: set_fields to set or empty fields of the record, create_record to make a record of another type, notify to tell people of the CRM Connector account in the app and by email, or a change action named as its propose_ tool without the prefix (update_fields, move_stage, assign_owner, add_note, add_task, update_task, log_activity, add_line_item, link_records, unlink_records and the others). One more is carried out by CRM Connector itself and is only switched on through the approval page: email_contact (a short email to the email address of the record's contact)."New value: +"set_fields, create_record, notify, email_contact (approved on its page only), or a propose_ tool's action without the prefix, such as add_task."
    • removedInput schema / properties / actions / items / properties / kind / enum
      Removed value: -[
      -  "set_fields",
      -  "create_record",
      -  "notify",
      -  "update_fields",
      -  "move_stage",
      -  "assign_owner",
      -  "add_note",
      -  "add_task",
      -  "update_task",
      -  "log_activity",
      -  "add_line_item",
      -  "send_record",
      -  "convert_estimate",
      -  "convert_lead",
      -  "link_records",
      -  "unlink_records",
      -  "create_item",
      -  "update_item",
      -  "set_item_state",
      -  "move_item",
      -  "add_tag",
      -  "remove_tag",
      -  "add_follower",
      -  "remove_follower",
      -  "add_to_workflow",
      -  "remove_from_workflow",
      -  "update_note",
      -  "send_message",
      -  "update_conversation",
      -  "record_payment",
      -  "change_consent",
      -  "void_record",
      -  "send_document",
      -  "email_contact"
      -]
    • addedInput schema / properties / actions / items / properties / kind / maxLength
      Added value: +40
    • changedInput schema / properties / actions / items / properties / set / description
      Previous value: -"For set_fields: field keys and their new values. For create_record: the fields of the new record, such as its contact as {record.id}. A date may be {today} or {today+3} (three days after the rule acts). {record.field:Amount} is the value a field of the record that fired holds when the rule acts."New value: +"For set_fields and create_record: field keys and values. Values may use {record.id}, {today}, {today+3} and {record.field:Amount}."
    • changedInput schema / properties / actions / items / properties / type / description
      Previous value: -"For create_record: the record type to make, such as opportunity."New value: +"For create_record: the record type to make."
    • changedInput schema / properties / apply_to_existing / description
      Previous value: -"Also act once on the records that already match when the rule is switched on. Off by default: the rule then only acts on what happens from now on."New value: +"Also act once on records that already match."
    • changedInput schema / properties / conditions / description
      Previous value: -"Only if: at most 5 conditions on the same record, all of which must hold. Leave it out when the rule always acts."New value: +"Only if: conditions that must all hold."
    • changedInput schema / properties / conditions / items / properties / field / description
      Previous value: -"The field key, as describe_record_type names it."New value: +"The field key."
    • changedInput schema / properties / conditions / items / properties / value / description
      Previous value: -"The value to compare with; not for empty and not_empty, and a number for above and below."New value: +"Not for empty and not_empty; a number for above and below."
    • changedInput schema / properties / conditions / items / properties / values / description
      Previous value: -"For one_of: the values the field may hold."New value: +"For one_of."
    • changedInput schema / properties / name / description
      Previous value: -"A short name for the rule, as the customer would call it."New value: +"A short name for the rule."
    • changedInput schema / properties / replaces / description
      Previous value: -"Optional: the id of an earlier automation of the same system that this rule replaces once it is approved."New value: +"Optional id of an automation this rule replaces once approved."
    • changedInput schema / properties / system / description
      Previous value: -"Which AI agent: the system's id from get_ai_agent_options, or the name of the system or its connection. Ask the person which AI agent they mean unless they named it in this conversation; never pick one yourself."New value: +"The AI agent: its system or connection name."
    • changedInput schema / properties / trigger / description
      Previous value: -"When the rule acts: created (a record of the type is made), becomes (a field gets a value, such as a deal becoming won), changes (a field changes in any way), date_reached (a date field of the record is a number of days before or after today, such as 3 days before the due date), unchanged_for (the record has not changed for a number of days, such as a deal stuck in a stage), tag_added or tag_removed (a tag is put on or taken off the record)."New value: +"When the rule acts."
    • changedInput schema / properties / trigger / properties / days / description
      Previous value: -"For date_reached: days after the date, negative for before it (-3 is three days before the due date, 30 is thirty days after it, 0 the day itself). For unchanged_for: the days without a change, at least 1."New value: +"For date_reached: days after the date, negative for before. For unchanged_for: days without a change."
    • changedInput schema / properties / trigger / properties / field / description
      Previous value: -"The field key, as describe_record_type names it. Needed for becomes, changes and date_reached (the date field); for unchanged_for only with a value it must hold; for a tag trigger left out unless the system keeps tags in a field of its own."New value: +"The field key. For becomes, changes and date_reached."
    • changedInput schema / properties / trigger / properties / kind / description
      Previous value: -"created, becomes, changes, date_reached, unchanged_for, tag_added or tag_removed."New value: +"created, becomes (a field gets a value), changes, date_reached, unchanged_for, tag_added or tag_removed."
    • changedInput schema / properties / trigger / properties / value / description
      Previous value: -"For becomes: the value the field must get, as the system stores it; leave it out for any value. For unchanged_for: the value the field holds while the record stands still, such as a stage. For tag_added and tag_removed: the tag."New value: +"For becomes: the value it gets. For unchanged_for: the value it holds. For a tag trigger: the tag."
    • changedInput schema / properties / trigger / properties / yearly / description
      Previous value: -"For date_reached: the date comes round every year, such as a birthday."New value: +"For date_reached: every year, such as a birthday."
    • changedInput schema / properties / type / description
      Previous value: -"The record type, as get_ai_agent_options lists it: contact, opportunity, invoice, estimate, job, appointment."New value: +"The record type, such as contact or invoice."
  2. Changed1 schema field changed
    • changedInput schema / properties / actions / items / properties / arguments / description
      Previous value: -"For a change action: one item of that action's propose_ tool, for the record that met the rule. Use {record.id} as its id and leave type out for the rule's own record type. To act on the contact of a record, give type contact with {record.contact} as its id; on its deal, type opportunity with {record.deal}; on its job, {record.job}. To act on what an earlier action of the rule made (create_record, convert_estimate, convert_lead), use {action1.id} for the first action. For assign_owner, users is a list of user ids that take turns, one per record. For notify: to is owners or the emails of members of the CRM Connector account (at most 5), text what to tell (at most 900 characters) and optionally subject; it tells at most 50 times a day. A date may be {today} or {today+3} (three days after the rule acts). {record.field:Amount} is the value a field of the record that fired holds when the rule acts. For email_contact: subject, body, sender_name (the From name shown, 2 to 60 characters) and reply_to (the address replies go to), both required. The subject and body may use {contact.first_name}, {contact.name}, {record.name}, {organisation}; the address it goes to is always the contact's own."New value: +"For a change action: one item of that action's propose_ tool, for the record that met the rule. Use {record.id} as its id and leave type out for the rule's own record type. To act on the contact of a record, give type contact with {record.contact} as its id; on its deal, type opportunity with {record.deal}; on its job, {record.job}. To act on what an earlier action of the rule made (create_record, convert_estimate, convert_lead), use {action1.id} for the first action. To give a task or record to the owner of the record that met the rule, use {record.owner} as its user. For assign_owner, users is a list of user ids that take turns, one per record. For notify: to is owners or the emails of members of the CRM Connector account (at most 5), text what to tell (at most 900 characters) and optionally subject; it tells at most 50 times a day. A date may be {today} or {today+3} (three days after the rule acts). {record.field:Amount} is the value a field of the record that fired holds when the rule acts. For email_contact: subject, body, sender_name (the From name shown, 2 to 60 characters) and reply_to (the address replies go to), both required. The subject and body may use {contact.first_name}, {contact.name}, {record.name}, {organisation}; the address it goes to is always the contact's own."
  3. Changed2 schema fields changed
    • changedInput schema / properties / system / description
      Previous value: -"Which AI agent: the system's id from get_ai_agents_info, or the name of the system or its connection. Ask the person which AI agent they mean unless they named it in this conversation; never pick one yourself."New value: +"Which AI agent: the system's id from get_ai_agent_options, or the name of the system or its connection. Ask the person which AI agent they mean unless they named it in this conversation; never pick one yourself."
    • changedInput schema / properties / type / description
      Previous value: -"The record type, as get_ai_agents_info lists it: contact, opportunity, invoice, estimate, job, appointment."New value: +"The record type, as get_ai_agent_options lists it: contact, opportunity, invoice, estimate, job, appointment."
  4. Changed2 schema fields changed
    • changedInput schema / properties / actions / items / properties / arguments / description
      Previous value: -"For the actions of propose_changes: one item of propose_changes with that action, for the record that met the rule. Use {record.id} as its id and leave type out for the rule's own record type. To act on the contact of a record, give type contact with {record.contact} as its id; on its deal, type opportunity with {record.deal}; on its job, {record.job}. To act on what an earlier action of the rule made (create_record, convert_estimate, convert_lead), use {action1.id} for the first action. For assign_owner, users is a list of user ids that take turns, one per record. For notify: to is owners or the emails of members of the CRM Connector account (at most 5), text what to tell (at most 900 characters) and optionally subject; it tells at most 50 times a day. A date may be {today} or {today+3} (three days after the rule acts). {record.field:Amount} is the value a field of the record that fired holds when the rule acts. For email_contact: subject, body, sender_name (the From name shown, 2 to 60 characters) and reply_to (the address replies go to), both required. The subject and body may use {contact.first_name}, {contact.name}, {record.name}, {organisation}; the address it goes to is always the contact's own."New value: +"For a change action: one item of that action's propose_ tool, for the record that met the rule. Use {record.id} as its id and leave type out for the rule's own record type. To act on the contact of a record, give type contact with {record.contact} as its id; on its deal, type opportunity with {record.deal}; on its job, {record.job}. To act on what an earlier action of the rule made (create_record, convert_estimate, convert_lead), use {action1.id} for the first action. For assign_owner, users is a list of user ids that take turns, one per record. For notify: to is owners or the emails of members of the CRM Connector account (at most 5), text what to tell (at most 900 characters) and optionally subject; it tells at most 50 times a day. A date may be {today} or {today+3} (three days after the rule acts). {record.field:Amount} is the value a field of the record that fired holds when the rule acts. For email_contact: subject, body, sender_name (the From name shown, 2 to 60 characters) and reply_to (the address replies go to), both required. The subject and body may use {contact.first_name}, {contact.name}, {record.name}, {organisation}; the address it goes to is always the contact's own."
    • changedInput schema / properties / actions / items / properties / kind / description
      Previous value: -"The action the rule applies by itself: set_fields to set or empty fields of the record, create_record to make a record of another type, notify to tell people of the CRM Connector account in the app and by email, or one of the actions of propose_changes (update_fields, move_stage, assign_owner, add_note, add_task, update_task, log_activity, add_line_item, link_records, unlink_records and the others). One more is carried out by CRM Connector itself and is only switched on through the approval page: email_contact (a short email to the email address of the record's contact)."New value: +"The action the rule applies by itself: set_fields to set or empty fields of the record, create_record to make a record of another type, notify to tell people of the CRM Connector account in the app and by email, or a change action named as its propose_ tool without the prefix (update_fields, move_stage, assign_owner, add_note, add_task, update_task, log_activity, add_line_item, link_records, unlink_records and the others). One more is carried out by CRM Connector itself and is only switched on through the approval page: email_contact (a short email to the email address of the record's contact)."
  5. Changed15 schema fields changed
    • changedInput schema / properties / actions / items / properties / arguments / description
      Previous value: -"For the other kinds: one item of propose_changes with that action, for the record that met the rule. Use {record.id} as its id and leave type out for the rule's own record type. To act on the contact of an opportunity or other record, give type contact with {record.contact} as its id. A date may be {today} or {today+3} (three days after the rule acts)."New value: +"For the actions of propose_changes: one item of propose_changes with that action, for the record that met the rule. Use {record.id} as its id and leave type out for the rule's own record type. To act on the contact of a record, give type contact with {record.contact} as its id; on its deal, type opportunity with {record.deal}; on its job, {record.job}. To act on what an earlier action of the rule made (create_record, convert_estimate, convert_lead), use {action1.id} for the first action. For assign_owner, users is a list of user ids that take turns, one per record. For notify: to is owners or the emails of members of the CRM Connector account (at most 5), text what to tell (at most 900 characters) and optionally subject; it tells at most 50 times a day. A date may be {today} or {today+3} (three days after the rule acts). {record.field:Amount} is the value a field of the record that fired holds when the rule acts. For email_contact: subject, body, sender_name (the From name shown, 2 to 60 characters) and reply_to (the address replies go to), both required. The subject and body may use {contact.first_name}, {contact.name}, {record.name}, {organisation}; the address it goes to is always the contact's own."
    • changedInput schema / properties / actions / items / properties / kind / description
      Previous value: -"The action the rule applies by itself, one of the actions of propose_changes: set_fields to set or empty fields of the record, or update_fields, move_stage, add_note, add_task, update_task, log_activity, add_line_item, link_records or unlink_records."New value: +"The action the rule applies by itself: set_fields to set or empty fields of the record, create_record to make a record of another type, notify to tell people of the CRM Connector account in the app and by email, or one of the actions of propose_changes (update_fields, move_stage, assign_owner, add_note, add_task, update_task, log_activity, add_line_item, link_records, unlink_records and the others). One more is carried out by CRM Connector itself and is only switched on through the approval page: email_contact (a short email to the email address of the record's contact)."
    • changedInput schema / properties / actions / items / properties / kind / enum
      Previous value: -[
      -  "set_fields",
      -  "update_fields",
      -  "move_stage",
      -  "add_note",
      -  "add_task",
      -  "update_task",
      -  "log_activity",
      -  "add_line_item",
      -  "send_record",
      -  "convert_estimate",
      -  "convert_lead",
      -  "link_records",
      -  "unlink_records",
      -  "create_item",
      -  "update_item",
      -  "set_item_state",
      -  "move_item",
      -  "add_tag",
      -  "remove_tag",
      -  "add_follower",
      -  "remove_follower",
      -  "add_to_workflow",
      -  "remove_from_workflow",
      -  "update_note",
      -  "send_message",
      -  "update_conversation",
      -  "record_payment",
      -  "change_consent",
      -  "void_record",
      -  "send_document"
      -]New value: +[
      +  "set_fields",
      +  "create_record",
      +  "notify",
      +  "update_fields",
      +  "move_stage",
      +  "assign_owner",
      +  "add_note",
      +  "add_task",
      +  "update_task",
      +  "log_activity",
      +  "add_line_item",
      +  "send_record",
      +  "convert_estimate",
      +  "convert_lead",
      +  "link_records",
      +  "unlink_records",
      +  "create_item",
      +  "update_item",
      +  "set_item_state",
      +  "move_item",
      +  "add_tag",
      +  "remove_tag",
      +  "add_follower",
      +  "remove_follower",
      +  "add_to_workflow",
      +  "remove_from_workflow",
      +  "update_note",
      +  "send_message",
      +  "update_conversation",
      +  "record_payment",
      +  "change_consent",
      +  "void_record",
      +  "send_document",
      +  "email_contact"
      +]
    • changedInput schema / properties / actions / items / properties / set / description
      Previous value: -"For set_fields: field keys and their new values. A date may be {today} or {today+3} (three days after the rule acts)."New value: +"For set_fields: field keys and their new values. For create_record: the fields of the new record, such as its contact as {record.id}. A date may be {today} or {today+3} (three days after the rule acts). {record.field:Amount} is the value a field of the record that fired holds when the rule acts."
    • addedInput schema / properties / actions / items / properties / type
      Added value: +{
      +  "description": "For create_record: the record type to make, such as opportunity.",
      +  "maxLength": 40,
      +  "type": "string"
      +}
    • changedInput schema / properties / trigger / description
      Previous value: -"When the rule acts: created (a record of the type is made), becomes (a field gets a value, such as a deal becoming won), or changes (a field changes in any way)."New value: +"When the rule acts: created (a record of the type is made), becomes (a field gets a value, such as a deal becoming won), changes (a field changes in any way), date_reached (a date field of the record is a number of days before or after today, such as 3 days before the due date), unchanged_for (the record has not changed for a number of days, such as a deal stuck in a stage), tag_added or tag_removed (a tag is put on or taken off the record)."
    • addedInput schema / properties / trigger / properties / days
      Added value: +{
      +  "description": "For date_reached: days after the date, negative for before it (-3 is three days before the due date, 30 is thirty days after it, 0 the day itself). For unchanged_for: the days without a change, at least 1.",
      +  "maximum": 365,
      +  "minimum": -365,
      +  "type": "integer"
      +}
    • changedInput schema / properties / trigger / properties / field / description
      Previous value: -"The field key, as describe_record_type names it. Needed for becomes and changes."New value: +"The field key, as describe_record_type names it. Needed for becomes, changes and date_reached (the date field); for unchanged_for only with a value it must hold; for a tag trigger left out unless the system keeps tags in a field of its own."
    • changedInput schema / properties / trigger / properties / kind / description
      Previous value: -"created, becomes or changes."New value: +"created, becomes, changes, date_reached, unchanged_for, tag_added or tag_removed."
    • changedInput schema / properties / trigger / properties / kind / enum
      Previous value: -[
      -  "created",
      -  "becomes",
      -  "changes"
      -]New value: +[
      +  "created",
      +  "becomes",
      +  "changes",
      +  "date_reached",
      +  "unchanged_for",
      +  "tag_added",
      +  "tag_removed"
      +]
    • changedInput schema / properties / trigger / properties / value / description
      Previous value: -"For becomes: the value the field must get, as the system stores it. Leave it out for any value."New value: +"For becomes: the value the field must get, as the system stores it; leave it out for any value. For unchanged_for: the value the field holds while the record stands still, such as a stage. For tag_added and tag_removed: the tag."
    • addedInput schema / properties / trigger / properties / yearly
      Added value: +{
      +  "description": "For date_reached: the date comes round every year, such as a birthday.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / rule / properties / actions / items / properties / type
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / rule / properties / trigger / properties / days
      Added value: +{
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / rule / properties / trigger / properties / yearly
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
  6. Changed1 schema field changed
    • changedInput schema / properties / actions / items / properties / kind / enum
      Previous value: -[
      -  "set_fields",
      -  "update_fields",
      -  "move_stage",
      -  "add_note",
      -  "add_task",
      -  "update_task",
      -  "log_activity",
      -  "add_line_item",
      -  "send_record",
      -  "convert_estimate",
      -  "link_records",
      -  "unlink_records"
      -]New value: +[
      +  "set_fields",
      +  "update_fields",
      +  "move_stage",
      +  "add_note",
      +  "add_task",
      +  "update_task",
      +  "log_activity",
      +  "add_line_item",
      +  "send_record",
      +  "convert_estimate",
      +  "convert_lead",
      +  "link_records",
      +  "unlink_records",
      +  "create_item",
      +  "update_item",
      +  "set_item_state",
      +  "move_item",
      +  "add_tag",
      +  "remove_tag",
      +  "add_follower",
      +  "remove_follower",
      +  "add_to_workflow",
      +  "remove_from_workflow",
      +  "update_note",
      +  "send_message",
      +  "update_conversation",
      +  "record_payment",
      +  "change_consent",
      +  "void_record",
      +  "send_document"
      +]
  7. Changed1 schema field changed
    • changedInput schema / properties / actions / items / properties / kind / enum
      Previous value: -[
      -  "set_fields",
      -  "update_fields",
      -  "move_stage",
      -  "add_note",
      -  "add_task",
      -  "update_task",
      -  "log_activity",
      -  "add_line_item",
      -  "link_records",
      -  "unlink_records"
      -]New value: +[
      +  "set_fields",
      +  "update_fields",
      +  "move_stage",
      +  "add_note",
      +  "add_task",
      +  "update_task",
      +  "log_activity",
      +  "add_line_item",
      +  "send_record",
      +  "convert_estimate",
      +  "link_records",
      +  "unlink_records"
      +]
  8. Changed2 schema fields changed
    • changedInput schema / properties / actions / items / properties / kind / description
      Previous value: -"The action the rule applies by itself, one of the actions of propose_changes: set_fields to set or empty fields of the record, or update_fields, move_stage, add_note, add_task, update_task, link_records or unlink_records."New value: +"The action the rule applies by itself, one of the actions of propose_changes: set_fields to set or empty fields of the record, or update_fields, move_stage, add_note, add_task, update_task, log_activity, add_line_item, link_records or unlink_records."
    • changedInput schema / properties / actions / items / properties / kind / enum
      Previous value: -[
      -  "set_fields",
      -  "update_fields",
      -  "move_stage",
      -  "add_note",
      -  "add_task",
      -  "update_task",
      -  "link_records",
      -  "unlink_records"
      -]New value: +[
      +  "set_fields",
      +  "update_fields",
      +  "move_stage",
      +  "add_note",
      +  "add_task",
      +  "update_task",
      +  "log_activity",
      +  "add_line_item",
      +  "link_records",
      +  "unlink_records"
      +]
  9. Changed3 schema fields changed
    • changedInput schema / properties / actions / items / properties / arguments / description
      Previous value: -"For the other kinds: one item of propose_changes with that action, for the record that met the rule. Use {record.id} as its id and leave type out for the rule's own record type. A date may be {today} or {today+3} (three days after the rule acts)."New value: +"For the other kinds: one item of propose_changes with that action, for the record that met the rule. Use {record.id} as its id and leave type out for the rule's own record type. To act on the contact of an opportunity or other record, give type contact with {record.contact} as its id. A date may be {today} or {today+3} (three days after the rule acts)."
    • changedInput schema / properties / system / description
      Previous value: -"Which AI agent: the system's id from list_ai_systems, or the name of the system or its connection. Ask the person which AI agent they mean unless they named it in this conversation; never pick one yourself."New value: +"Which AI agent: the system's id from get_ai_agents_info, or the name of the system or its connection. Ask the person which AI agent they mean unless they named it in this conversation; never pick one yourself."
    • changedInput schema / properties / type / description
      Previous value: -"The record type, as list_ai_systems lists it: contact, opportunity, invoice, estimate, job, appointment."New value: +"The record type, as get_ai_agents_info lists it: contact, opportunity, invoice, estimate, job, appointment."
  10. Changed2 schema fields changed
    • changedInput schema / properties / actions / items / properties / kind / description
      Previous value: -"The action the rule applies by itself, one of the actions of propose_changes: set_fields to set or empty fields of the record, or update_fields, move_stage, add_note, add_task, link_records or unlink_records."New value: +"The action the rule applies by itself, one of the actions of propose_changes: set_fields to set or empty fields of the record, or update_fields, move_stage, add_note, add_task, update_task, link_records or unlink_records."
    • changedInput schema / properties / actions / items / properties / kind / enum
      Previous value: -[
      -  "set_fields",
      -  "update_fields",
      -  "move_stage",
      -  "add_note",
      -  "add_task",
      -  "link_records",
      -  "unlink_records"
      -]New value: +[
      +  "set_fields",
      +  "update_fields",
      +  "move_stage",
      +  "add_note",
      +  "add_task",
      +  "update_task",
      +  "link_records",
      +  "unlink_records"
      +]
  11. Changed2 schema fields changed
    • changedInput schema / properties / actions / items / properties / arguments / description
      Previous value: -"For the other kinds: one item of its propose tool, for the record that met the rule. Use {record.id} as its id and leave type out for the rule's own record type. A date may be {today} or {today+3} (three days after the rule acts)."New value: +"For the other kinds: one item of propose_changes with that action, for the record that met the rule. Use {record.id} as its id and leave type out for the rule's own record type. A date may be {today} or {today+3} (three days after the rule acts)."
    • changedInput schema / properties / actions / items / properties / kind / description
      Previous value: -"set_fields to set or empty fields of the record, or the action of a propose tool, which the rule applies by itself: update_fields (propose_field_update), move_stage (propose_stage_move), add_note (propose_note), add_task (propose_task), link_records (propose_link) or unlink_records (propose_unlink)."New value: +"The action the rule applies by itself, one of the actions of propose_changes: set_fields to set or empty fields of the record, or update_fields, move_stage, add_note, add_task, link_records or unlink_records."
  12. First observed

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only flag destructiveHint/openWorldHint; the description adds the crucial behavior that nothing runs until approved, that sending rules are switched on only via the link, and that a 30-day dry-run is returned. It also names the prerequisite source for field keys (describe_record_type), which no annotation conveys.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with an audience tag and the use condition, then the outcome, then the follow-up, then exclusions — a sensible order with no filler. The semicolon-chained sentences are dense and slightly harder to parse than they need to be, but every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nested, 8-parameter mutation with an output schema, the description covers the safety model, the approval workflow, the prerequisite tool, and the alternatives. Nothing an agent needs in order to decide or invoke is missing, and return values are legitimately left to the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description genuinely adds meaning by pointing to describe_record_type as the source of field keys and by framing the three structural parts (when / only if / then) that map onto trigger, conditions, and actions. It does not restate the per-field details, which is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — it writes one rule (when, only if, then) on one record type — and immediately says what comes back (a sentence, a 30-day backtest, an approval link). It explicitly rules out the propose_* one-off tools and plan_integration, so an agent can route correctly without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit use condition ("the person wants something to keep happening by itself in one system") with a concrete example, plus two named exclusions with the alternatives to use instead. It also states the required follow-up call (set_automation_status with approve) after the person says yes.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources