Skip to main content
Glama

Créer ou modifier un contact

dandori_save_contact

Créer un contact (sans id, name obligatoire) ou modifier un contact existant (avec id ; seuls les champs fournis changent). Sans Plus, le nombre est limité (le refus le dit).

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": "dandori_save_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoID du contact à modifier ; absent pour en créer un
nameNoNom (obligatoire à la création)
tagsNoNoms des tags (remplacent les tags actuels)
emailNo
notesNo
phoneNo
birthdayNoDate de naissance (YYYY-MM-DD)
categoryNo
nicknameNoSurnom
relationshipNoRelation (ex. sœur, collègue de Paul)
create_important_dateNoCréation seulement : ajoute l'anniversaire aux dates importantes
desired_frequency_daysNoTous les combien de jours se donner des nouvelles

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (non-read-only, non-destructive, non-idempotent), it discloses the important partial-update behavior ('seuls les champs fournis changent') and a plan-based quota that can cause rejection. It leaves out whether a created contact's id is returned, which an agent would want given idempotentHint=false.

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?

One compact sentence with parenthetical clauses, front-loading the create/update branch. The quota note ('le refus le dit') is slightly cryptic and appended rather than integrated.

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?

For a 12-parameter mutation tool with no output schema, the description covers mode selection and the free-plan limit but says nothing about what is returned or about side effects like create_important_date. Adequate, but with clear gaps an agent must discover by trial.

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?

With 67% schema coverage, the description adds real meaning about the two pivotal parameters: `id` toggles create vs update and `name` is mandatory only at creation. It does not clarify the remaining fields' semantics (e.g. whether `tags` replace the existing set), which the schema partially covers.

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 states a specific verb+resource (créer/modifier un contact) and explains the two operating modes via the presence or absence of `id`. It clearly distinguishes create from update, though it does not contrast itself with sibling tools such as dandori_log_contact_interaction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit conditions: no `id` means creation with `name` required; with `id` means partial update where only supplied fields change. It stops short of naming alternatives or excluding adjacent uses (e.g. logging an interaction), so it is clear context but not full when/when-not guidance.

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