Skip to main content
Glama
Sign In

CRM Connector

by com.crm-connector
OverviewDiscussionsAdmin

Propose: Move an item

propose_move_item

AI Agents (inside one system): Use when the person asks for this in a system whose AI agent may change records: An item moved to another list, group or place, such as a project task to another list. Give one item per record, at most 25. Nothing is written yet: the answer shows, per record, what it holds now and would hold after, plus a proposal id. Show it to the person, say so first when something would be sent to the people in their system, ask whether to go ahead, and only then call apply_proposal; when needsApproval is true, share the approve link instead. Not for reading (use search_records or get_record).

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>",
      "items": "<items>"
    },
    "name": "propose_move_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesOne object per record, at most 25.
systemYesWhich 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.

Output Schema

NameRequiredDescriptionDefault
noticeNo
changesYes
systemIdYes
warningsYes
expiresAtYes
approveUrlYes
proposalIdYes
systemNameYes
needsApprovalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / items / items / properties / item_kind / enum
      Previous value: -[
-  "business",
-  "contact_person",
-  "custom_record",
-  "object",
-  "link_type",
-  "link",
-  "product",
-  "price",
-  "product_collection",
-  "coupon",
-  "order",
-  "transaction",
-  "subscription",
-  "invoice_schedule",
-  "invoice_template",
-  "calendar",
-  "calendar_group",
-  "calendar_resource",
-  "blocked_slot",
-  "service",
-  "booking",
-  "pipeline",
-  "custom_field",
-  "custom_value",
-  "location_tag",
-  "template",
-  "location",
-  "user",
-  "project",
-  "project_task",
-  "recurring_task",
-  "comment",
-  "document",
-  "document_template",
-  "workflow",
-  "workflow_log",
-  "form",
-  "form_submission",
-  "survey",
-  "survey_submission",
-  "campaign",
-  "conversation",
-  "price_list",
-  "credit_note",
-  "retainer_invoice",
-  "sales_receipt",
-  "debit_note",
-  "delivery_challan",
-  "time_entry",
-  "expense",
-  "recurring_expense",
-  "bill",
-  "recurring_bill",
-  "purchase_order",
-  "purchase_return",
-  "vendor",
-  "vendor_payment",
-  "vendor_credit",
-  "journal",
-  "account",
-  "tax",
-  "currency",
-  "bank_account"
-]New value: +[
+  "business",
+  "contact_person",
+  "lead",
+  "custom_record",
+  "object",
+  "link_type",
+  "link",
+  "product",
+  "price",
+  "product_collection",
+  "coupon",
+  "order",
+  "transaction",
+  "subscription",
+  "invoice_schedule",
+  "invoice_template",
+  "calendar",
+  "calendar_group",
+  "calendar_resource",
+  "blocked_slot",
+  "service",
+  "booking",
+  "pipeline",
+  "custom_field",
+  "custom_value",
+  "location_tag",
+  "template",
+  "location",
+  "user",
+  "report",
+  "project",
+  "project_task",
+  "recurring_task",
+  "comment",
+  "document",
+  "document_template",
+  "workflow",
+  "workflow_log",
+  "form",
+  "form_submission",
+  "survey",
+  "survey_submission",
+  "campaign",
+  "conversation",
+  "group",
+  "macro",
+  "view",
+  "article",
+  "satisfaction_rating",
+  "price_list",
+  "credit_note",
+  "retainer_invoice",
+  "sales_receipt",
+  "debit_note",
+  "delivery_challan",
+  "time_entry",
+  "expense",
+  "recurring_expense",
+  "bill",
+  "recurring_bill",
+  "purchase_order",
+  "purchase_return",
+  "vendor",
+  "vendor_payment",
+  "vendor_credit",
+  "journal",
+  "account",
+  "tax",
+  "currency",
+  "bank_account"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / items / items / properties / item_kind / enum
      Previous value: -[
-  "business",
-  "custom_record",
-  "object",
-  "link_type",
-  "link",
-  "product",
-  "price",
-  "product_collection",
-  "coupon",
-  "order",
-  "transaction",
-  "subscription",
-  "invoice_schedule",
-  "invoice_template",
-  "calendar",
-  "calendar_group",
-  "calendar_resource",
-  "blocked_slot",
-  "service",
-  "booking",
-  "pipeline",
-  "custom_field",
-  "custom_value",
-  "location_tag",
-  "template",
-  "location",
-  "user",
-  "project",
-  "project_task",
-  "recurring_task",
-  "comment",
-  "document",
-  "document_template",
-  "workflow",
-  "workflow_log",
-  "form",
-  "form_submission",
-  "survey",
-  "survey_submission",
-  "campaign",
-  "conversation",
-  "price_list",
-  "credit_note",
-  "retainer_invoice",
-  "sales_receipt",
-  "debit_note",
-  "delivery_challan",
-  "time_entry",
-  "expense",
-  "recurring_expense",
-  "bill",
-  "recurring_bill",
-  "purchase_order",
-  "purchase_return",
-  "vendor",
-  "vendor_payment",
-  "vendor_credit",
-  "journal",
-  "account",
-  "tax",
-  "currency",
-  "bank_account"
-]New value: +[
+  "business",
+  "contact_person",
+  "custom_record",
+  "object",
+  "link_type",
+  "link",
+  "product",
+  "price",
+  "product_collection",
+  "coupon",
+  "order",
+  "transaction",
+  "subscription",
+  "invoice_schedule",
+  "invoice_template",
+  "calendar",
+  "calendar_group",
+  "calendar_resource",
+  "blocked_slot",
+  "service",
+  "booking",
+  "pipeline",
+  "custom_field",
+  "custom_value",
+  "location_tag",
+  "template",
+  "location",
+  "user",
+  "project",
+  "project_task",
+  "recurring_task",
+  "comment",
+  "document",
+  "document_template",
+  "workflow",
+  "workflow_log",
+  "form",
+  "form_submission",
+  "survey",
+  "survey_submission",
+  "campaign",
+  "conversation",
+  "price_list",
+  "credit_note",
+  "retainer_invoice",
+  "sales_receipt",
+  "debit_note",
+  "delivery_challan",
+  "time_entry",
+  "expense",
+  "recurring_expense",
+  "bill",
+  "recurring_bill",
+  "purchase_order",
+  "purchase_return",
+  "vendor",
+  "vendor_payment",
+  "vendor_credit",
+  "journal",
+  "account",
+  "tax",
+  "currency",
+  "bank_account"
+]
    • changedInput schema / properties / items / items / properties / parent / description
      Previous value: -"The item it sits in, where the kind needs one: the object of a custom record, the product of a price, the project of a task, the task of a comment."New value: +"The item it sits in, where the kind needs one: the object of a custom record, the product of a price, the contact of a contact person, the project of a task or time entry, the task or project of a comment."
  3. Changed1 schema field 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."
  4. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description adds substantial context on top: nothing is written until apply_proposal, the response contains per-record before/after state plus a proposal id, a needsApproval flag may appear, and some moves notify people in the system. That notification side effect is exactly the kind of behavior annotations cannot express.

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?

Dense and front-loaded, with the purpose stated first and the workflow, constraints, and exclusions following in a logical order. The opening framing ('Use when the person asks for this in a system whose AI agent may change records') is slightly circuitous before the actual action is named, which costs a bit of immediacy.

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?

An output schema exists, yet the description still summarizes what the answer holds (current state, proposed state, proposal id), which helps the agent narrate it to the person. For a 2-parameter proposal tool with a large item_kind enum, the agent has everything needed to call it and to handle the approval branch.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters (system, items) and the nested item_kind/item_id/to/parent fields are already fully documented in the schema. The description restates the batching rule ('one item per record, at most 25') and the system-selection rule, both of which already appear in the schema, so it adds little new meaning. Baseline 3 applies when the schema carries the parameter burden.

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

Purpose4/5

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

States a specific verb and resource ('An item moved to another list, group or place, such as a project task to another list') and explicitly excludes reading tasks by naming search_records and get_record. An agent can tell what the tool produces (a proposal, not a write). It stops short of differentiating itself from the closest sibling, propose_move_stage, so it is clear but not maximally discriminating.

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 explicit when-to-use context ('when the person asks for this in a system whose AI agent may change records'), an end-to-end workflow (show the proposal, flag outbound notifications, ask for confirmation, then call apply_proposal), and a branch for needsApproval=true where the approve link is shared instead. It also names the read alternatives and says what this tool is not for.

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

All CRM Connector toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources