Capable

Log touch

log_touch

Record an activity (call / email / meeting / LinkedIn). MUST link to at least one of account_id, contact_id, opportunity_id (auto-resolve names with search_* before calling — never invent ids). Recorder- and scheduler-captured meetings file themselves as touches automatically — when the touch already exists, don't stop at "already logged": process it (its transcript when the call was recorded, the user's notes otherwise) and propose updates for approval (propose_updates with source_touch_id → review_proposed_updates). Returns the created row. Supply request_id (UUID) plus occurred_at for a durable retry. For a recorded outbound sequence step, include sequence_action:{enrollment_id,step}; the saved activity advances that exact step through the same governed update and returns sequence_tracking (updated, pending or unchanged). Retrying the same request repairs a pending update without another activity.

When to use: After any meaningful interaction. commit_reviewed_updates often applies this from an approved review.

Example: Log a 45-min discovery call with Sarah at Acme yesterday — covered pain, impact, decision criteria.

Input Schema

TableJSON Schema

Name	Required	Description
`type`	Yes	Defaults: call \| email \| meeting \| linkedin \| other. A workspace admin may rename or add values — see the live set in propose_updates' workspace.enum_values, or an admin's describe_schema.
`source`	No	Defaults: manual \| transcript_paste \| api \| mcp \| inbox_import \| calendar_import \| imported_csv \| scheduler \| recorder \| reply_io \| instantly. A workspace admin may rename or add values — see the live set in propose_updates' workspace.enum_values, or an admin's describe_schema.
`subject`	No	Short title of the activity (an email's subject line, a meeting's title); searchable and part of the duplicate fingerprint.
`summary`	No	Plain-text account of what happened or was discussed — the rep's notes for an unrecorded call; searchable together with the subject.
`direction`	No	Defaults: inbound \| outbound. A workspace admin may rename or add values — see the live set in propose_updates' workspace.enum_values, or an admin's describe_schema.
`account_id`	No	A uuid.
`contact_id`	No	A uuid.
`request_id`	No	A uuid.
`occurred_at`	No	An ISO 8601 datetime.
`participants`	No	Email addresses of the people on the activity (sender or recipients, meeting attendees), stored as a flat list and matched by participant search.
`custom_fields`	No	Values for the workspace's custom touch fields, keyed by field key (see describe_schema); the reserved capable_sequence_action key is refused — use sequence_action.
`opportunity_id`	No	A uuid.
`sequence_action`	No	Completes a sequence step: {enrollment_id: uuid, step: the person's current step}; needs request_id, contact_id, occurred_at, direction 'outbound' and the step's channel as type.
`duration_minutes`	No	An integer ≥ 0.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`touch`	No
`account`	No
`sequence_tracking`	No
`duplicate_suppressed`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 6, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations only cover the basic write-safety profile (readOnly=false, idempotent=false, destructive=false). The description adds genuinely non-obvious behavior: auto-filed recorder/scheduler meetings, the request_id+occurred_at durable-retry contract, and the sequence_action side effect that advances an enrollment step and returns sequence_tracking. The retry note does not contradict idempotentHint=false, since durability depends on supplying request_id.

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?

Front-loaded with the core action and clear paragraph breaks for preconditions, duplicate handling, retry, and sequencing. It is dense and long, and the 'Example' line adds little an agent needs for invocation, but nearly every sentence carries operational information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 14-parameter mutation tool with nested objects and an output schema already documenting the return, the description covers the remaining gaps an agent needs: required linkage, id resolution, duplicate/sequence side effects, and retry semantics.

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 the baseline is 3, but the description adds real meaning: why request_id exists (durable retry), the outbound/contact/occurred_at prerequisites for sequence_action, and the prohibition on the reserved capable_sequence_action custom-field key.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb (Record) and enumerated resource types (call/email/meeting/LinkedIn), and routes to distinct siblings (search_*, propose_updates, commit_reviewed_updates) so an agent can separate it from add_note, update_record, or propose_updates.

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

Usage Guidelines5/5

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

Explicit when-to-use ('After any meaningful interaction'), explicit precondition (MUST link to at least one account/contact/opportunity), explicit anti-pattern ('never invent ids'), and a dedicated duplicate-handling path telling the agent not to stop at 'already logged' but to process and propose updates.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Capable tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?