Skip to main content
Glama

Log outreach and optionally schedule a follow-up

log_outreach

Record that you texted, called or left a voicemail for a contact, and optionally create a dated follow-up task. The follow-up date is computed in this account timezone, not UTC.

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>",
      "channel": "<channel>"
    },
    "name": "log_outreach"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelYesHow you reached out
contact_idYesThe contact id
contact_nameNoName to write into the log line
followup_daysNoCreate a follow-up task this many days from today; omit for no follow-up

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?

Annotations already cover the safety profile (write, non-destructive, closed-world). The description adds a genuinely non-obvious behavioral fact beyond them: the follow-up date is computed in the account timezone, not UTC. It does not disclose what the call returns (log entry, task id) or whether the log entry is deduplicated.

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?

Two sentences, zero waste. The core action is front-loaded and the timezone caveat is placed immediately after the follow-up clause it qualifies.

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 four-parameter write with no output schema, the description covers what is recorded, the channels available, and the follow-up semantics including timezone handling. Only the response shape / side effects on the contact record are left implicit, which is a minor gap at this complexity.

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 coverage is 100%, so baseline is 3; the description earns an extra point by clarifying that followup_days resolves against the account timezone rather than UTC, which the schema description ('this many days from today') leaves ambiguous. It says nothing extra about channel or contact_name beyond their schema descriptions.

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 and resource ('Record that you texted, called or left a voicemail for a contact') and names the optional side effect (creating a follow-up task). It is concrete enough to distinguish from create_task or log_activity, but it never explicitly names those siblings as alternatives.

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 rather than stated: the reader infers this is the tool for after an outreach attempt, and that followup_days is the way to schedule follow-up work instead of calling create_task. There is no explicit when-to-use/when-not or named alternative.

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