Skip to main content
Glama
Sign In

Widely

by com.widely-mobile
OverviewDiscussionsAdmin

Create a contact

create_contact

Adds one saved contact on this seat. name is required. phone_numbers and emails are optional. The same arguments add another contact. An existing contact stays as it is.

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

Input Schema

NameRequiredDescriptionDefault
nameYesContact name.
emailsNoEmail addresses to save. Each item is an address, or an object with address and an optional type.
phone_numbersNoPhone numbers to save. Each item is a number, or an object with number and an optional type such as mobile, home, or work.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), and the description usefully corroborates the non-idempotent behavior (repeating the same call creates another contact) and states that existing contacts are untouched. That is real added context beyond the annotations, though it omits what the call returns.

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?

Four short sentences with the core fact (creates one contact, name required) front-loaded and no filler. The phrasing "the same arguments add another contact" is slightly ambiguous but earns its place as a duplication warning.

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

Completeness4/5

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

For a simple 3-parameter create with full schema coverage and clear annotations, this is nearly sufficient. The one gap is that no output schema exists and the description never says what comes back (e.g., the new contact's identifier), which an agent would need for follow-up calls.

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 description coverage is 100%, so the schema already documents name, emails, and phone_numbers in detail. The description only restates required vs optional, adding no format, constraint, or edge-case detail; baseline 3 applies.

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?

"Adds one saved contact on this seat" gives a specific verb (adds) and resource (contact) plus a scoping qualifier (one, on this seat), so the agent knows this is a single-record creation tool. It does not explicitly name or differentiate itself from siblings like update_contact or search_contacts, which keeps it at 4.

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?

"The same arguments add another contact" and "An existing contact stays as it is" imply that this is an append-only create, not an upsert, which nudges the agent away from update_contact. However, there is no explicit when-to-use/when-not-to-use statement or named alternative, so guidance is inferred rather than stated.

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

All Widely toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources