Skip to main content
Glama
Sign In
Headquarter

Headquarter

by axeldotdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_client

Register a new client by providing name, address, website, email, and phone number.

Instructions

Create a new client

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

Input Schema

NameRequiredDescriptionDefault
nameYesClient name
emailNoClient email
phoneNoClient phone number
addressNoClient address
websiteNoClient website URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only says 'Create' which implies mutation but does not disclose side effects, idempotency, error cases, or what happens on duplicate names or missing required fields. No output schema to indicate return value.

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

Conciseness4/5

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

The description is a single, front-loaded sentence with no wasted words. However, it could be expanded to include essential context without losing conciseness.

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?

For a creation tool with 5 parameters and no output schema, the description should explain what is created, what is returned, and any constraints (e.g., uniqueness of name). It lacks this information, making it incomplete.

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 each parameter already has a description. The tool description adds no extra meaning beyond 'Create a new client'. Baseline score of 3 is appropriate as the schema does the work.

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 client' which is a specific verb+resource. It distinguishes from sibling tools like create_contact or create_issue by its unique resource. However, it does not add any additional context about what a client is or special aspects.

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 this tool versus alternatives like update_client or delete_client. No mention of prerequisites, required permissions, or scenarios where create_client is appropriate versus other actions.

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