Skip to main content
Glama
Sign In
Karbon MCP Server

Karbon MCP Server

by Mad-Man-Dan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get custom field values

get_custom_field_values

Retrieve custom field values for contacts, organizations, or client groups using their entity key.

Instructions

Get the custom field values set on a specific entity (contact, organization, or client group) by its entity key.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entityKey": "<entityKey>"
    },
    "name": "get_custom_field_values"
  }
}

Input Schema

NameRequiredDescriptionDefault
entityKeyYesThe ContactKey, OrganizationKey, or ClientGroupKey

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.3

TDQS

A3.6/5.0
Behavior3/5

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

The description indicates a read operation without destructive side effects, but with no annotations provided, it should disclose more: e.g., what happens if entity does not exist, authentication requirements, or if values are returned as a list or map.

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?

One sentence, efficient and front-loaded with the key information. Could be slightly more structured, but no unnecessary content.

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

Completeness3/5

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

Given the simple parameter and lack of output schema, the description is adequate but does not clarify the return format (e.g., a map of field IDs to values) or edge cases. Slightly incomplete for an agent to fully understand the response.

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 input schema has 100% description coverage; the description repeats the schema's explanation of entityKey types. No additional semantic detail is added beyond what the schema provides.

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?

The description clearly states the action (get), the resource (custom field values), and the entity types (contact, organization, client group). It is distinct from sibling tools like 'get_custom_field' (which retrieves the field definition) and 'set_custom_field_values' (write operation).

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

Usage Guidelines3/5

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

The description explains what entity types are supported but does not provide when to use this tool versus alternatives (e.g., when to prefer this over getting the entity itself). No explicit when-not or alternatives are mentioned.

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

Deploy Server

Other Tools