Skip to main content
Glama
Sign In
Whatify MCP Server

Whatify MCP Server

by ashusingh1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

whatify_create_contact

Create a new contact or update an existing one by phone number, with support for name, email, tags, and custom attributes.

Instructions

Create a new contact, or update-and-return an existing one with the same phone number.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
tagsNo
emailNo
phoneYes
country_codeNo
custom_attributesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations provided; description only states upsert behavior. Does not disclose permissions, rate limits, destructive potential, or what happens on conflict beyond 'update-and-return'. Minimal transparency.

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 depth. Front-loaded with main behavior, but no structure for parameter details. Could be expanded without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 6 parameters, no output schema, no annotations, the description is insufficient. Missing details on return value, parameter usage, required fields beyond phone, and edge cases. Incomplete for effective tool use.

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

Parameters1/5

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

Schema has 0% description coverage for 6 parameters. Description adds no explanations for any parameter (e.g., name, tags, email, country_code, custom_attributes). Agent must rely solely on parameter names.

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?

Describes upsert behavior ('create a new contact, or update-and-return an existing one with the same phone number') with a specific verb and resource. Distinguishes from sibling 'whatify_update_contact' by clarifying it handles creation and upsert.

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 use for creating or updating contacts by phone, but no explicit when-to-use or when-not-to-use. Lacks alternatives or exclusions, leaving the agent to infer that separate update tool exists.

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