Skip to main content
Glama

fluentcrm_custom_fields

Retrieve custom fields from FluentCRM to extend contact data and personalize marketing automation workflows.

Instructions

Pobiera pola niestandardowe

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP server tool handler switch case for 'fluentcrm_custom_fields' that invokes the FluentCRMClient's listCustomFields method and returns the JSON-stringified result as text content.
    case 'fluentcrm_custom_fields':
      return { content: [{ type: 'text', text: JSON.stringify(await client.listCustomFields(), null, 2) }] };
  • Registration of the 'fluentcrm_custom_fields' tool in the ListTools response, including name, description, and empty input schema.
      name: 'fluentcrm_custom_fields',
      description: 'Pobiera pola niestandardowe',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Input schema definition for the 'fluentcrm_custom_fields' tool, which accepts an empty object (no parameters required).
    inputSchema: {
      type: 'object',
      properties: {},
    },
  • FluentCRMClient helper method that fetches the list of custom fields by making a GET request to the '/custom-fields' API endpoint.
    async listCustomFields() {
      const response = await this.apiClient.get('/custom-fields');
      return response.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. It states 'retrieves', implying a read-only operation, but doesn't disclose behavioral traits such as authentication needs, rate limits, error handling, or what 'custom fields' entails (e.g., format, pagination). For a 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.

Conciseness4/5

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

The description is a single, efficient phrase ('Pobiera pola niestandardowe') that directly states the action and resource. It's appropriately sized for a simple tool with no parameters, though it could be more structured (e.g., by specifying context). Every word earns its place, but it's slightly under-specified rather than concise.

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 no annotations, no output schema, and 0 parameters, the description is incomplete. It lacks details on what 'custom fields' includes (e.g., types, usage), behavioral context, or return values. For a retrieval tool in a CRM context, this leaves significant gaps for an AI agent to understand its full utility.

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?

The input schema has 0 parameters with 100% coverage, so no parameters need documentation. The description doesn't add parameter details, which is acceptable since there are none to explain. A baseline of 4 is appropriate as it doesn't need to compensate for any schema gaps.

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 'Pobiera pola niestandardowe' (Polish for 'Retrieves custom fields') states a verb ('retrieves') and resource ('custom fields'), providing a basic purpose. However, it lacks specificity about what type of custom fields (e.g., contact fields, campaign fields) and doesn't distinguish from siblings like 'fluentcrm_list_tags' or 'fluentcrm_list_contacts', which are also retrieval operations. The purpose is clear but vague in scope.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites, context (e.g., for configuring contacts or campaigns), or exclusions. With siblings like 'fluentcrm_list_contacts' that might involve custom fields, the description offers no differentiation, leaving usage unclear.

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