Skip to main content
Glama

Propose: Make another item

propose_create_item

AI Agents (inside one system): Use when the person asks for this in a system whose AI agent may change records: A new item next to the six record types, such as a product, a coupon, a custom record, a project task or a custom field, with the values its kind takes. A system looks for the same item first and makes none when it exists. 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_create_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.2/5.0
Behavior5/5

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

The annotations only declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false; the description adds substantial behavior the annotations cannot convey: nothing is written at propose time, the response shows per-record before/after values plus a proposal id, the system deduplicates and creates nothing when an identical item exists, and the batch caps at 25. It also discloses a non-obvious side effect risk ('say so first when something would be sent to the people in their system') and the approval/link flow, which an agent could not infer from the structured fields.

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

Conciseness3/5

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

Length is defensible for a tool with an approval workflow, and the key constraint (nothing is written yet) is delivered early, but the prose is a single dense run-on with nested clauses ('Use when the person asks for this in a system whose AI agent may change records: A new item next to the six record types...'). The colon-chained sentence makes the agent parse several ideas at once, and 'A new item next to the six record types' is vague phrasing that costs more than it saves.

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

Completeness4/5

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

An output schema exists and the description still usefully signals what comes back (per-record current vs. prospective values plus a proposal id), and it covers the limit, dedupe check, secondary user-notification risk, and the handoff to apply_proposal / approve link. For a batchable, open-world mutation proposal this is close to complete; the only remaining gap is kind-specific value requirements, which the agent would have to discover from get_item.

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 the schema already documents both `system` and `items` (including the 200-char limit, the parent field and the kind enum), making 3 the baseline. The description does little beyond that: it restates the one-item-per-record and at-most-25 rules already encoded in the array schema and says values are those 'its kind takes', without clarifying per-kind required values or how a malformed item is reported.

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?

The definition makes clear that the tool creates a proposal to add a new record item of a given kind (product, coupon, custom record, project task, custom field), with the values the kind takes, and that the answer is a proposal id rather than a write. It also draws the line against reading (search_records / get_record) and against execution (apply_proposal). The opening clause 'AI Agents (inside one system): Use when the person asks for this...' is an audience/usage framing rather than a clean verb+resource statement, which slightly muddies the first line an agent reads.

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?

It gives explicit when-to-use ('when the person asks for this in a system whose AI agent may change records'), explicit when-not ('Not for reading'), and names both the alternative for reading and the alternative for execution, including the sequencing rule that apply_proposal is only called after the person approves. It further covers the needsApproval branch (share the approve link instead) and that the agent must ask the person which AI agent/system they mean rather than choosing one itself.

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