CRM Connector

Propose: Send a document or contract

propose_send_document

AI Agents (inside one system): Use when the person asks for this in a system whose AI agent may change records: A document or contract sent for signing from the person's own system, either one that exists or a new one made from a template for a contact. The recipients receive it, and only the person can approve it. 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_send_document"
  }
}

Input Schema

Name	Required	Description	Default
`items`	Yes	One object per record, at most 25.
`system`	Yes	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.

Output Schema

Name	Required	Description	Default
`notice`	No
`changes`	Yes
`systemId`	Yes
`warnings`	Yes
`expiresAt`	Yes
`approveUrl`	Yes
`proposalId`	Yes
`systemName`	Yes
`needsApproval`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

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."

AddedNov 5, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare the generic profile (not read-only, not destructive, open-world, not idempotent). The description adds substantive behavior beyond that: nothing is written at proposal time, the response shows per-record current vs. would-be state plus a proposal id, recipients actually receive the document, only the person can approve, and there is a 25-item batch cap.

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?

The usage trigger is front-loaded and every sentence carries operational content. It is a single dense paragraph with some run-on phrasing ('A document or contract sent for signing from the person's own system, either one that exists or a new one made from a template for a contact'), which costs readability but not substance.

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 proposal/mutation tool with an output schema, the description covers the safety-relevant flow (dry-run, human confirmation, approval link), the batch limit, and the routing away from read tools. Nothing an agent needs to invoke it correctly or safely is missing.

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 nested item fields and the system id are already documented in the schema. The description restates the batch constraint ('one item per record, at most 25') which duplicates maxItems/minItems rather than adding meaning, and it adds nothing about how 'system' is resolved beyond what the schema already says.

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?

The description names a specific verb and resource — sending a document or contract for signing from the person's own system, either an existing document or one generated from a template for a contact. It also distinguishes itself from reading tools by naming search_records and get_record, and from other send-style siblings via the document/contract framing.

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 an explicit trigger ('Use when the person asks for this in a system whose AI agent may change records'), an explicit exclusion ('Not for reading — use search_records or get_record'), and the required follow-up path: show the proposal, confirm with the person, then call apply_proposal, or share the approve link when needsApproval is true. Alternatives and sequencing are both spelled out.

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

All CRM Connector tools Inspect

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

Need Help?