Skip to main content
Glama
Sign In
kickserv-mcp

kickserv-mcp

by Willbrownfield007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

list_customers

List customers filtered by name, contact, email, or address. Use a free-text search to find specific customer records.

Instructions

List customers, optionally filtered by a search term (name, contact, email, or address).

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

Input Schema

NameRequiredDescriptionDefault
searchNoFree-text filter, e.g. 'Rivera' or 'Austin'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description is minimal, stating only 'List customers' which implies a read operation. It lacks details on return limits, pagination, or side effects, but is adequate for a simple list.

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, front-loaded sentence with no wasted words; every part is informative.

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?

No output schema exists, and the description does not mention return structure or count. However, for a list tool, the description is acceptable but could hint at the response format.

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?

The schema already describes the 'search' parameter (100% coverage), but the description adds value by specifying the fields searched (name, contact, email, address), providing context beyond the schema's 'Free-text filter'.

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 verb 'List' and resource 'customers', and specifies the optional filtering capability with fields (name, contact, email, or address), distinguishing it from the sibling get_customer.

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?

Implies usage when listing customers with optional filtering, but provides no when-not-to-use guidance or explicit alternatives like get_customer for a single record.

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