Skip to main content
Glama

fluentcrm_get_contact

Retrieve contact details from FluentCRM marketing automation by providing a subscriber ID to access specific contact information.

Instructions

Pobiera szczegóły konkretnego kontaktu

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subscriberIdYesID kontaktu

Implementation Reference

  • Core implementation of the tool: fetches contact details from FluentCRM REST API endpoint /subscribers/{subscriberId} using Axios client.
    async getContact(subscriberId: number) {
      const response = await this.apiClient.get(`/subscribers/${subscriberId}`);
      return response.data;
    }
  • Tool registration in the ListTools response, defining name, description, and input schema.
      name: 'fluentcrm_get_contact',
      description: 'Pobiera szczegóły konkretnego kontaktu',
      inputSchema: {
        type: 'object',
        properties: {
          subscriberId: { type: 'number', description: 'ID kontaktu' },
        },
        required: ['subscriberId'],
      },
    },
  • Input schema validation: requires subscriberId as number.
    inputSchema: {
      type: 'object',
      properties: {
        subscriberId: { type: 'number', description: 'ID kontaktu' },
      },
      required: ['subscriberId'],
    },
  • MCP server dispatch handler: calls the FluentCRMClient.getContact method with tool arguments and formats response.
    case 'fluentcrm_get_contact':
      return { content: [{ type: 'text', text: JSON.stringify(await client.getContact((args as any)?.subscriberId), null, 2) }] };
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. The description only states what the tool does ('retrieves details') without adding any behavioral context. It doesn't mention whether this is a read-only operation, what permissions might be required, potential errors (e.g., if the contact doesn't exist), or the format of returned details. 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, concise sentence ('Pobiera szczegóły konkretnego kontaktu') that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action, making it efficient. However, it could be slightly more informative without sacrificing brevity, such as by hinting at the parameter usage.

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 lack of annotations and output schema, the description is incomplete. It doesn't provide enough context for an AI agent to fully understand how to use the tool effectively. For example, it doesn't describe what 'details' are returned, potential error conditions, or how this tool fits into the broader context of contact management with sibling tools. This leaves gaps in understanding the tool's behavior and output.

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?

The schema description coverage is 100%, with the parameter 'subscriberId' fully documented in the schema as 'ID kontaktu' (contact ID). The description doesn't add any meaning beyond this, as it doesn't explain what 'subscriberId' represents or provide additional context. Given the high schema coverage, the baseline score of 3 is appropriate, as the schema already handles parameter documentation adequately.

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 states the purpose ('Pobiera szczegóły konkretnego kontaktu' translates to 'Retrieves details of a specific contact'), which is clear but basic. It specifies the verb ('retrieves') and resource ('contact details'), but doesn't differentiate from sibling tools like 'fluentcrm_find_contact_by_email' or 'fluentcrm_list_contacts', which also retrieve contact information. The description is not tautological but lacks specificity about what distinguishes this tool.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention that this tool is for retrieving a single contact by ID, as opposed to 'fluentcrm_find_contact_by_email' (which uses email) or 'fluentcrm_list_contacts' (which lists multiple contacts). There's no explicit or implied context for usage, leaving the agent to infer from the tool name and schema alone.

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