Skip to main content
Glama
Sign In

LiveCRM

by ai.livecrm
OverviewDiscussionsAdmin

Set Too-Long Text

set_too_long_text

Set what LiveCRM does with a text value longer than the CRM field it is written to. Every value is checked against what the connected CRM accepts before it is written, and a field that does not fit is left out while the rest of the record is written. 'skip', how every connection starts, leaves a too-long text out like any other value that does not fit. 'truncate' cuts it to the field's length and writes it. list_crm_connections shows each connection's current setting. It changes later writes only; nothing already written changes.

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>",
      "too_long_text": "<too_long_text>"
    },
    "name": "set_too_long_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
connection_idYesThe CRM connection. Call list_crm_connections first.
too_long_textYes'skip' or 'truncate'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), it discloses that every value is validated against the CRM before writing, non-fitting fields are omitted while the rest of the record is written, and the setting only affects later writes. The statement that nothing already written changes corroborates the non-destructive hint rather than contradicting it.

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

Conciseness5/5

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

Purpose is front-loaded in sentence one, followed by the validation rule, the two enum behaviors, the inspection sibling, and the forward-only scope. Every sentence carries distinct information, and passives are used consistently rather than padding.

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 two-parameter mutation with no output schema, the description covers the semantics, default, and scope of change thoroughly. It does not say what the call returns or whether it echoes the newly stored setting, a minor omission given the absence of an output schema.

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 coverage is 100%, so the baseline is 3, and the description earns an upgrade by explaining what each enum value actually does to the write: 'skip' leaves the too-long value out like any other non-fitting value, 'truncate' cuts it to field length and writes it. Only connection_id is left to the schema.

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 first sentence states a specific verb and resource: it configures what LiveCRM does with text longer than the target CRM field. It also distinguishes this write-configuration tool from the read-side sibling by pointing to list_crm_connections for inspecting each connection's current setting.

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?

It explains that 'skip' is the starting default for every connection and that list_crm_connections shows the current value, which tells an agent when this tool is relevant. It stops short of explicit when-not guidance or stating prerequisites beyond the schema's 'Call list_crm_connections first' note.

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