FavCRM

This connector has been deprecated

This connector has been replaced by https://glama.ai/mcp/connectors/io.favcrm/favcrm/admin

clone

Duplicate an existing record (product, tier, campaign, post, service package, promotion, gift offer). Creates a copy in DRAFT status with "(Copy)" appended to the name.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Override the name of the cloned entity (defaults to "Original Name (Copy)")
`entityId`	Yes	ID of the entity to clone
`entityType`	Yes	Type of entity to clone

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Tool result payload — shape varies per tool, see the tool description
`summary`	Yes	One-line human-readable summary of the action
`renderType`	Yes	UI rendering hint for the result

TDQS

A4.4/5.0

Behavior5/5

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

Discloses key behavioral traits: duplication, default name change, DRAFT status creation. Annotations (readOnlyHint: false, destructiveHint: false) are consistent, and description adds valuable context beyond annotations.

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?

Single, focused sentence conveying core behavior without redundancy. Front-loads action ('Duplicate an existing record') and follows with specifics.

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?

Covers essential behavior; output schema exists so return values need not be described. Could mention error cases (e.g., entity not found) but not necessary for basic usage.

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% with clear parameter descriptions. Description does not add new semantic meaning beyond the schema, but confirms default name behavior for the 'name' parameter.

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?

Clearly states it duplicates an existing record, lists supported entity types, and describes key transformation (DRAFT status, '(Copy)' appended). Unambiguous and distinct from create/update siblings.

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?

Implies usage when needing a copy of an existing record, implicitly contrasting with create_* (new from scratch) and update_* (modify existing). No explicit when-not-to-use, but context is clear.

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

All FavCRM tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation5/5

Each tool targets a distinct resource and action, with clear descriptions that minimize ambiguity. Even related tools like create_post vs create_post_type are well-separated by their targets.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern (e.g., create_account, list_services, update_post), with no mixing of naming conventions. The pattern is predictable throughout the set.

Tool Count1/5

190 tools is excessively large for any server, far exceeding the typical 3-15 tool range. The sheer volume overwhelms agents and suggests poor scoping, even for a comprehensive CRM platform.

Completeness4/5

The tool set covers CRUD operations across many domains (CRM, bookings, marketing, CMS, etc.), but notable gaps exist (e.g., no delete_account, delete_contact, update_booking). These are minor given the vast surface.

Resources

Need Help?