Skip to main content
Glama
daanno

Simplicate MCP Server

by daanno

get_custom_fields

Retrieve custom field definitions for specific models like organizations, persons, or projects to access extended data fields in your business system.

Instructions

Retrieve custom field definitions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoModel type (organization, person, project, etc.)

Implementation Reference

  • MCP server tool handler for 'get_custom_fields' that calls the Simplicate service method and returns JSON-formatted result.
    case 'get_custom_fields': {
      const data = await this.simplicateService.getCustomFields(toolArgs.model);
      return { content: [{ type: 'text', text: JSON.stringify(data, null, 2) }] };
  • Registration of the 'get_custom_fields' tool in the MCP server's listTools handler, including schema.
      name: 'get_custom_fields',
      description: 'Retrieve custom field definitions',
      inputSchema: {
        type: 'object',
        properties: {
          model: { type: 'string', description: 'Model type (organization, person, project, etc.)' },
        },
      },
    },
  • Helper method implementing the core logic for retrieving custom fields via Simplicate API.
    async getCustomFields(model?: string): Promise<SimplicateCustomField[]> {
      try {
        const params = model ? { model } : undefined;
        const response = await this.client.get('/customfields/customfield', params);
        return response.data || [];
      } catch (error) {
        // Custom Fields endpoint may require specific model parameter
        console.warn('getCustomFields: endpoint returned error, returning empty array');
        return [];
      }
    }
  • TypeScript interface defining the structure of custom field objects.
      id: string;
      name: string;
      type: string;
      model: string;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Retrieve' implies a read operation, but it doesn't disclose behavioral traits like authentication requirements, rate limits, response format, or pagination. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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 with zero waste. It's front-loaded and directly states the tool's purpose without unnecessary elaboration, making it easy to parse quickly.

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 and no output schema, the description is incomplete. It doesn't explain what 'custom field definitions' entail, the return format, or any error conditions. For a retrieval tool in a context with many siblings, more context is needed to guide effective use.

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 description coverage is 100%, with the single parameter 'model' fully documented in the schema. The description adds no additional meaning beyond what the schema provides, such as examples or constraints. Baseline 3 is appropriate since the schema handles parameter documentation adequately.

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

Purpose4/5

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

The description clearly states the verb ('Retrieve') and resource ('custom field definitions'), making the purpose immediately understandable. However, it doesn't differentiate this tool from other 'get_' siblings like get_organizations or get_persons beyond the resource type, missing explicit sibling differentiation.

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. With many sibling tools (e.g., get_organizations, get_persons), there's no indication of context, prerequisites, or exclusions for retrieving custom fields versus other data types.

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/daanno/simplicate-mcp'

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