Skip to main content
Glama

LiveCRM

by ai.livecrm
OverviewDiscussionsAdmin

Create Normalization Run

create_normalize_run

Create a run that rewrites field values into canonical form -- phone formats, country and state names, street abbreviations, company-name suffixes -- and WRITES the result to the CRM when dispatched. Preview the rules with preview_normalize_scheme first. WHICH RULES: the template_id you name, or the connection's Default when you name none. The Default is seeded per connection and a person authors it. A JOB-SCOPED TIDY-UP AUTHORS ITS OWN SCHEME AND NAMES IT. 'Tidy up the titles on these contacts' is a rule for THIS run, so create_rule_template a normalize template and pass its id here. EDITING THE DEFAULT INSTEAD CHANGES EVERY OTHER NORMALIZE RUN on the connection, including ones this request has nothing to do with. A person may genuinely mean to change their default -- that is a different request, and worth saying out loud before doing it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesA name for the run, shown in the Runs tab. It writes canonical values to the CRM.
dispositionNoWho releases this run's writes. 'execute' dispatches the pass on request, which is the default and what every run has always done. 'queue' stamps the run awaiting_approval and launches nothing until a person approves it. 'propose' dispatches the pass, which computes everything and writes NOTHING to the CRM, putting one reviewable proposal in the queue per record it would have changed — so a person approves the changes one at a time instead of the run wholesale. A credential may ask for either form of review and may never release it. Note that 'propose' still SPENDS what computing spends: an enrichment set to propose buys the provider data and then queues the writes, because a value nobody fetched cannot be proposed.execute
filter_specNoWhich records this run covers, as a filter tree. Omit for the whole object. It DESCRIBES a population and is resolved when the run is DISPATCHED, so write what you mean -- the CRO at Skypoint is `account_name is Skypoint AND title contains CRO` -- and never look a record up to write one. You need no ids and no counts. Call list_filterable_fields first, for the field names and operators only.
object_typeYesWhich CRM object the run targets: contact, account or lead.
template_idNoThe normalize scheme this run applies, by id (list_rule_templates). Omit to use the connection's Default scheme.
connection_idYesThe CRM connection. Required. Call list_crm_connections to get one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / template_id / description
      Added value: +"The normalize scheme this run applies, by id (list_rule_templates). Omit to use the connection's Default scheme."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only give readOnlyHint=false / destructiveHint=false, which would not tell an agent that this tool writes to the CRM on dispatch. The description supplies that: creation stages a run and the WRITE happens when dispatched, the Default is connection-scoped and person-authored, and editing it has blast radius across unrelated runs. This is exactly the context annotations cannot carry.

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 the core purpose and dispatch behavior, then the rule-selection guidance. Dense but every block carries a decision the agent must make. The heavy all-caps emphasis and the closing aside about what 'a person may genuinely mean' add rhetorical weight that a tighter phrasing could carry.

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?

No output schema exists, and the description does not say what is returned on creation (e.g., a run id for later dispatch/get_run), which an agent orchestrating create-then-dispatch would want. Otherwise it is complete for a write-triggering creation tool: target object, filter semantics, rule selection, and review dispositions are all addressed.

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 description coverage is 100%, so the baseline is 3; the description still adds meaning by framing template_id as 'the scheme this run applies' and explaining the Default fallback is per-connection and authored by a person, which helps an agent reason about omitting it. It does not add much about disposition or filter_spec beyond what the schema already spells out.

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?

Specific verb + resource + effect: 'Create a run that rewrites field values into canonical form ... and WRITES the result to the CRM when dispatched,' with a concrete enumeration of what normalization covers (phones, country/state, street abbreviations, company suffixes). This distinguishes it clearly from the many sibling run-creation tools (dedup, enrichment, assignment, verification).

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?

Explicit when-to-use guidance: preview rules with preview_normalize_scheme first, use template_id or fall through to the connection Default, and a clear routing rule to create_rule_template for a job-scoped tidy-up. It also names the anti-pattern (editing the Default) with the consequence (changing every other normalize run on the connection).

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

All LiveCRM 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