Skip to main content
Glama
Sign In
Karbon MCP Server

Karbon MCP Server

by Mad-Man-Dan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List contacts

list_contacts

List or search person contacts in Karbon with OData filtering by name or contact type.

Instructions

List or search person contacts in Karbon. Supports OData filtering, e.g. filter: "contains(FullName,'Smith')" or "ContactType eq 'Client'".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoMax results to return (1-100, default 100)
skipNoNumber of results to skip, for pagination
filterNoOData $filter expression, e.g. "contains(FullName,'Smith')" or "PrimaryStatus eq 'InProgress'". Operators: eq, ne, gt, ge, lt, le, and, or, contains().
orderbyNoOData $orderby, e.g. "LastModifiedDateTime desc"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Despite no annotations, the description clearly indicates a read-only list/search operation with OData support. Does not mention pagination or rate limits, but schema handles pagination params. No contradictions.

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?

Single sentence front-loaded with purpose, followed by concise example. No filler or repetition.

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

Completeness4/5

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

Sufficient for a simple list tool with well-documented parameters. No output schema, but expected response is a list of contacts; not critical to specify. Could mention pagination behavior, but top/skip are explained in schema.

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?

Schema descriptions cover all 4 parameters (100% coverage), so baseline is 3. Description adds value by providing concrete OData filter examples and explaining the filter parameter's usage beyond schema syntax.

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?

Description clearly states 'List or search person contacts in Karbon', providing specific verb and resource. Distinguishes from sibling tools like get_contact (single contact) and create/update_contact.

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

Usage Guidelines4/5

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

Implies usage for listing/searching with OData filtering, and gives concrete filter examples. Lacks explicit when-to-use vs alternative tools (e.g., when to use get_contact instead), but sufficient for a list operation.

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