Skip to main content
Glama

fluentcrm_validate_smart_link_data

Validate Smart Link data before creation in FluentCRM to ensure proper configuration and prevent errors.

Instructions

Waliduje dane Smart Link przed utworzeniem

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesNazwa Smart Link
slugNoSlug
target_urlYesDocelowy URL
apply_tagsNo
apply_listsNo
remove_tagsNo
remove_listsNo
auto_loginNo

Implementation Reference

  • Core handler function implementing the Smart Link data validation logic in the FluentCRMClient class. Validates title, target_url (required string, http protocol), and optional slug format.
    validateSmartLinkData(data: any): { valid: boolean; errors: string[] } {
      const errors: string[] = [];
      
      if (!data.title || typeof data.title !== 'string') {
        errors.push('Title is required and must be a string');
      }
      
      if (!data.target_url || typeof data.target_url !== 'string') {
        errors.push('Target URL is required and must be a string');
      }
      
      if (data.target_url && !data.target_url.startsWith('http')) {
        errors.push('Target URL must start with http:// or https://');
      }
      
      if (data.slug && !/^[a-z0-9-]+$/.test(data.slug)) {
        errors.push('Slug must contain only lowercase letters, numbers, and hyphens');
      }
      
      return {
        valid: errors.length === 0,
        errors
      };
    }
  • Tool registration in the MCP server's ListToolsRequestSchema handler, defining name, description, and input schema.
    {
      name: 'fluentcrm_validate_smart_link_data',
      description: 'Waliduje dane Smart Link przed utworzeniem',
      inputSchema: {
        type: 'object',
        properties: {
          title: { type: 'string', description: 'Nazwa Smart Link' },
          slug: { type: 'string', description: 'Slug' },
          target_url: { type: 'string', description: 'Docelowy URL' },
          apply_tags: { type: 'array', items: { type: 'number' } },
          apply_lists: { type: 'array', items: { type: 'number' } },
          remove_tags: { type: 'array', items: { type: 'number' } },
          remove_lists: { type: 'array', items: { type: 'number' } },
          auto_login: { type: 'boolean' },
        },
        required: ['title', 'target_url'],
      },
    },
  • Input schema definition for the tool, specifying properties and required fields.
    inputSchema: {
      type: 'object',
      properties: {
        title: { type: 'string', description: 'Nazwa Smart Link' },
        slug: { type: 'string', description: 'Slug' },
        target_url: { type: 'string', description: 'Docelowy URL' },
        apply_tags: { type: 'array', items: { type: 'number' } },
        apply_lists: { type: 'array', items: { type: 'number' } },
        remove_tags: { type: 'array', items: { type: 'number' } },
        remove_lists: { type: 'array', items: { type: 'number' } },
        auto_login: { type: 'boolean' },
      },
      required: ['title', 'target_url'],
    },
  • MCP server dispatch handler for the tool call, invoking the client.validateSmartLinkData method.
    case 'fluentcrm_validate_smart_link_data':
      return { content: [{ type: 'text', text: JSON.stringify(client.validateSmartLinkData(args as any), null, 2) }] };
  • Comment indicating the validateSmartLinkData is a helper utility.
    // Helper method to validate Smart Link data
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool validates data, but doesn't describe what happens during validation—such as whether it returns errors, warnings, or a success status, or if it performs side effects like checking database constraints. For a validation tool with zero annotation coverage, this is a significant gap in transparency.

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?

The description is a single, efficient sentence in Polish that directly states the tool's function. It's appropriately sized and front-loaded with no wasted words, making it easy to understand at a glance despite the language barrier.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of 8 parameters with low schema coverage, no annotations, and no output schema, the description is incomplete. It doesn't explain what validation entails, what the output might be (e.g., success/failure, error messages), or how parameters interact. For a validation tool with rich input but poor documentation, this is inadequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is low at 38%, with only 3 of 8 parameters having descriptions in the schema. The description doesn't add any parameter-specific information beyond what the schema provides, failing to compensate for the coverage gap. It doesn't explain the meaning of parameters like 'apply_tags', 'auto_login', or the arrays, leaving them undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Waliduje dane Smart Link przed utworzeniem' (Polish for 'Validates Smart Link data before creation') states the purpose as validating data, but it's somewhat vague. It specifies the resource (Smart Link data) and timing (before creation), but doesn't clearly distinguish from sibling tools like 'fluentcrm_create_smart_link' beyond the validation aspect. The description is adequate but lacks specificity about what validation entails.

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

Usage Guidelines2/5

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

The description implies usage before creation ('przed utworzeniem'), suggesting it should be used prior to 'fluentcrm_create_smart_link'. However, it doesn't provide explicit guidance on when to use this tool versus alternatives, such as whether validation is mandatory or optional, or if there are other validation methods. No exclusions or clear alternatives are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/netflyapp/fluentcrm-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server