Skip to main content
Glama
Sign In

LiveCRM

by ai.livecrm
OverviewDiscussionsAdmin

Get Default Rule Configuration

get_default_rule_config
Read-only

The configuration a seeded Default template holds before anyone edits it, for a given tool, object and kind. Useful for telling an edited rule apart from an untouched one, and for explaining what a Default actually does. Served for the deduplication kinds (matching, master_record, survivorship) and for normalize; anything else answers 404. Reading it changes nothing -- it does not reset a template, which would be authoring.

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": {
      "connection_id": "<connection_id>",
      "tool_type": "<tool_type>",
      "object_type": "<object_type>"
    },
    "name": "get_default_rule_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoRequired for deduplication; omit for normalize, which has none.
tool_typeYesWhich tool's default.
object_typeYesWhich object: contact, account or lead, or lead_to_contact for a Lead to Contact deduplication default.
connection_idYesThe CRM connection. Call list_crm_connections first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / object_type / description
      Previous value: -"Which object: contact, account or lead."New value: +"Which object: contact, account or lead, or lead_to_contact for a Lead to Contact deduplication default."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and non-destructive, so the safety profile is covered; the description adds genuinely new behavior: which kinds are served, that unsupported kinds return 404, and explicitly that this call is not a reset operation. A brief note on whether a default always exists or what the payload looks like would complete it.

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?

Three sentences, front-loaded with the definition, then the use case, then the behavioral caveats. The opening clause ('The configuration a seeded Default template holds before anyone edits it') is slightly convoluted but every sentence earns its place.

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?

For a read-only getter with a fully described schema and no output schema, the definition covers scope, valid inputs, and failure behavior. It leaves the returned configuration's shape unstated, though the 'before anyone edits it' framing gives enough of a mental model to call it correctly.

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 coverage is 100%, including enum values and a description for connection_id pointing at list_crm_connections, so the schema does the heavy lifting. The description restates the tool/object/kind triple and reinforces the 404 condition for unsupported kinds, but adds no new syntax or format detail beyond the schema.

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 resource: the pre-edit configuration of a seeded Default template, scoped to a tool, object and kind. The contrast with an edited rule implicitly separates it from the template-editing siblings, but no sibling is named explicitly, so differentiation is left to inference.

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

Usage Guidelines4/5

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

Gives clear use cases (telling an edited rule from an untouched one, explaining what a Default does) and a hard boundary: only the deduplication kinds and normalize are served, everything else is 404. It also rules out a plausible misuse by saying reading does not reset a template. It stops short of naming an alternative tool for the edited/template case.

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