Skip to main content
Glama
Sign In
Karbon MCP Server

Karbon MCP Server

by Mad-Man-Dan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List teams

list_teams

List teams in Karbon with optional OData filtering to retrieve specific teams by name or attributes.

Instructions

List teams in Karbon (read-only). Supports OData filtering, e.g. filter: "contains(Name,'Tax')".

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_teams"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
skipNo
filterNoOData $filter expression

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.3

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description fully carries behavioral disclosure. It correctly states the tool is read-only and supports OData filtering, but does not explain pagination behavior (e.g., default 'top', max limit) or response structure, which would be helpful for an agent.

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 two concise sentences with no extraneous text. The first sentence states the core purpose and read-only nature, and the second provides a filtering example. It is front-loaded and efficient.

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?

Given the tool's simplicity and lack of output schema, the description covers the key aspects: read-only, list scope, and filtering. However, it could mention pagination limits or the return format (array of teams) to be more complete.

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 description adds meaning for the 'filter' parameter with a concrete example, but does not describe 'top' or 'skip' parameters, which lack descriptions in the schema. Schema coverage is low (33%), and the description only partially compensates.

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 tool lists teams in Karbon, specifies it is read-only, and provides an example of OData filtering. It distinguishes itself from 'get_team' and other list tools by indicating the scope and filtering capability.

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?

The description indicates read-only usage and gives a filtering example, implying use for listing teams. However, it lacks explicit guidance on when not to use this tool (e.g., when needing a single team via 'get_team') or alternatives.

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