Skip to main content
Glama
Sign In
kickserv-mcp

kickserv-mcp

by Willbrownfield007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

create_job

Create a new job record for a customer. Requires customer ID and job name; optionally include description and estimated total.

Instructions

Create a new job for a customer. Returns the created job record.

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": {
      "customer_id": "<customer_id>",
      "name": "<name>"
    },
    "name": "create_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesShort job title, e.g. 'Kitchen sink clog'
estimateNoEstimated total in dollars
customer_idYes
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations exist, so description must bear full load. Only states 'create' (mutation) and 'returns created record', but omits permissions, side effects, or idempotency, leaving agent underinformed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is concise but lacks substance for a 4-parameter creation tool. Appropriate length for minimal clarity but under-specified.

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?

No output schema; description mentions return of 'created job record' but provides no detail on fields, errors, or behavior. Incomplete for a mutation tool with complex parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%; only name and estimate have descriptions. The description adds no parameter information beyond schema, failing to cover undocumented customer_id and description.

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?

Description clearly states 'create a new job' with verb and resource, distinguishing from sibling read/list tools. However, lacks specificity on job scope, earning a 4 rather than 5.

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?

No guidance on when to use or prerequisites, and no mention of alternatives. Agent must infer from name alone, which is insufficient.

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