Skip to main content
Glama

Outil.io

Log activity

log_activity

Inscrire une activité sur un prospect ou un contact. kind : call (appel passé par le client à partir du script préparé), meeting, note, letter (courrier), email, sms, visit, other ; outcome : reached, no_answer, voicemail, callback, meeting_booked, interested, not_interested, sent, done ; at (défaut maintenant) ; nextActionAt AAAA-MM-JJ[THH:MM] devient la prochaine relance du prospect (null = plus de relance). Met à jour lastContactedAt et followUpNote du prospect. requestId stable évite les doublons.

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": {
      "kind": "<kind>"
    },
    "name": "log_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNo
kindYes
noteNo
dealIdNo
outcomeNo
contactIdNo
requestIdNo
prospectIdNo
nextActionAtNo
durationMinutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare it is a non-read-only, non-destructive, closed-world mutation; the description goes further by disclosing concrete side effects (lastContactedAt and followUpNote are updated on the prospect) and idempotency behavior via a stable requestId. It also states the default for `at` (now) and the null semantics for clearing a follow-up. It stops short of stating required permissions or how conflicting concurrent writes are handled.

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?

The purpose is front-loaded in the first clause, and the semicolon-delimited field notes are dense but scannable for a tool with 10 parameters. It is telegraphic rather than wasteful, though the heavy punctuation makes some clauses (the `call` parenthetical) harder to parse than necessary.

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 10-parameter mutation with no output schema, the description covers the highest-risk semantics: side effects, follow-up scheduling, and duplicate prevention. Gaps remain on the target-selection rules (must one of prospectId/contactId/dealId be supplied?) and on durationMinutes, but nothing critical to a correct call is missing.

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?

Schema description coverage is 0% across 10 parameters, so the description carries the burden and does substantial work: it disambiguates the `call` enum member, enumerates valid outcomes, gives the AAAA-MM-JJ[THH:MM] format for nextActionAt, and explains requestId as a deduplication key of at least 8 characters. It adds little for note, dealId, durationMinutes, or how prospectId/contactId/dealId relate as targets beyond "sur un prospect ou un contact".

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 first sentence names a specific verb and resource ("Inscrire une activité") and the target entities (prospect ou contact), which is far more precise than the title alone. It does not explicitly contrast with siblings such as get_site_activity (read) or batch_actions, so the differentiation is inferable from the write framing rather than stated.

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?

Usage is implied by the field documentation — choosing a `kind`, an `outcome`, and optionally setting a follow-up — but there is no explicit statement of when to call this versus related tools, nor any prerequisite or exclusion. An agent can infer the context but must reason about it.

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.