Skip to main content
Glama

HonestCRM

Log a call

log_call

Record a phone call on the timeline of a contact, company or deal.

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": {
      "target": "<target>",
      "outcome": "<outcome>"
    },
    "name": "log_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoWhat was discussed.
targetYesThe record the note or call belongs to.
outcomeYesHow the call went.
occurredAtNoWhen the call happened, as an ISO 8601 date and time. Default: now.
durationMinutesNoHow long the call lasted, in minutes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds that the entry lands on the target's timeline, which is useful placement context, but says nothing about duplicate creation (non-idempotent), permissions, or side effects like automations firing.

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?

A single front-loaded sentence with zero filler. It is efficient, though its brevity leaves it doing less work than a mutation tool of this shape could support.

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 5-parameter mutation with a nested target object and no output schema, the description omits what happens on success, whether repeated calls create duplicates, and how it differs from add_note. The rich schema compensates for parameter gaps, but behavioral completeness is only minimally adequate.

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%, with enum values, UUID format and the occurredAt default of "now" all documented in the schema itself. The description adds no meaning beyond that, so 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?

States a specific verb ("Record a phone call") and the resource it attaches to, including the three valid target record kinds. It is clear enough to separate from generic note tools, though it never names or contrasts the closest sibling (add_note).

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

Usage Guidelines2/5

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

The description gives no when-to-use or when-not-to-use guidance, no prerequisites, and no mention of the obvious alternative add_note for non-call timeline entries. Usage is only implied by the word "call".

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