Skip to main content
Glama

create_contact

Idempotent

Create a contact in the approved business. Reuse requestId when retrying the same creation.

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>",
      "requestId": "<requestId>"
    },
    "name": "create_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
typeNolead
emailNo
phoneNo
addressNo
companyNo
followUpNo
requestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false and idempotentHint=true, so the safety profile is covered. The description's requestId retry advice adds practical context on how to exploit idempotency, but it does not say what happens on a repeated requestId (error vs. returning the existing contact) or what the response contains.

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?

Two short sentences with zero filler, and the core action is front-loaded before the retry caveat. Brevity here is efficient rather than padded, though it leaves the definition thin.

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?

This is a mutation tool with 8 parameters, no schema descriptions and no output schema, so the description should explain field expectations and the result of a call. Instead it covers only the action and the retry mechanism, leaving an agent to guess at the semantics of most inputs and all outputs.

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 description coverage is 0% across 8 parameters, so the description carries the burden of explaining them and only mentions requestId. Field names like name, email, phone, company and followUp are largely self-explanatory, but nothing clarifies type defaults (lead), accepted enum values, or the meaning of followUp versus the separate set_contact_follow_up tool.

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 uses a specific verb+resource ("Create a contact") and scopes it to "the approved business", so an agent knows exactly what is produced. It does not, however, contrast itself with nearby siblings such as update_contact_profile or add_contact_note, so differentiation relies on the name alone.

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?

The only guidance is retry behavior ("Reuse requestId when retrying the same creation"), which is operational rather than selective. There is no statement of when to use this instead of updating an existing contact or when creation should be avoided (e.g., duplicate detection).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources