Skip to main content
Glama
Sign In
Karbon MCP Server

Karbon MCP Server

by Mad-Man-Dan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List work templates

list_work_templates

Retrieve work templates from your Karbon account to use with create_work_item. Supports filtering, pagination, and sorting.

Instructions

List work templates available on this account. Use a WorkTemplateKey with create_work_item to create templated work.

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

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

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It omits details like pagination behavior, read-only nature, or rate limits, though the schema partially covers pagination params.

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 sentences, front-loaded, and contains no unnecessary words. Every sentence serves a purpose.

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?

With 4 parameters, 100% schema coverage, and no output schema, the description is adequate but lacks details on return format or error conditions, which could be added for completeness.

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 coverage is 100%, so the description adds no additional meaning beyond the schema. The baseline of 3 applies as the schema already documents all parameters.

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 tool lists work templates on the account. It uses a specific verb and resource, distinguishing it from other list tools, though it doesn't explicitly contrast with siblings.

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 hints at usage by mentioning 'Use a WorkTemplateKey with create_work_item to create templated work,' but it doesn't specify when to prefer this over other list tools or address prerequisites.

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