Skip to main content
Glama

Noter un échange

dandori_log_contact_interaction

Noter un échange avec un contact (appel, rencontre, message) : remet à zéro le compteur « à recontacter ».

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": {
      "contact_id": "<contact_id>",
      "type": "<type>"
    },
    "name": "dandori_log_contact_interaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesin_person, call, message, mail ou autre
notesNoCe qui s'est dit
contact_idYesID du contact
interacted_atNoQuand (YYYY-MM-DD ou YYYY-MM-DD HH:MM), jamais dans le futur ; par défaut maintenant

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare a non-readOnly, non-destructive, non-idempotent write with no open-world access. The description adds the specific side effect of resetting the 'à recontacter' counter, but does not explain record creation, duplicate handling, or other write behavior beyond that.

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

Conciseness5/5

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

A single front-loaded sentence names the action, lists examples, and states the key side effect with no filler. Every clause earns its place.

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 four-parameter write tool with full schema coverage and annotations, the description supplies both the purpose and the counter-reset consequence. It omits return behavior and edge cases like duplicate interactions, but with no output schema and rich parameter docs it is close to sufficient.

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 contact_id, notes, interacted_at, and the type enum are already fully documented. The description's examples ('appel, rencontre, message') restate some enum values but add no syntax, constraints, or meaning beyond the schema, so the baseline of 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?

States a specific verb-resource ('Noter un échange avec un contact') and gives interaction examples, so the action is clear. It does not explicitly differentiate itself from sibling tools such as dandori_save_contact, so it falls short of the sibling distinction required for a 5.

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 phrase 'remet à zéro le compteur « à recontacter »' implies this tool is used after any contact interaction. However, there is no explicit when-to-use/when-not-to-use guidance or named alternative, leaving usage only implied.

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