Skip to main content
Glama

set_contact_follow_up

Set or clear a contact's follow-up date using the current contact revision.

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": {
      "id": "<id>",
      "revision": "<revision>",
      "requestId": "<requestId>",
      "date": "<date>"
    },
    "name": "set_contact_follow_up"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
dateYes
revisionYes
requestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already state that this is a write operation: readOnlyHint=false, destructiveHint=false, openWorldHint=false. The phrase 'using the current contact revision' adds real information by showing there is an optimistic-concurrency check. However, the description does not say what happens when the revision is stale, what the requestId does, or whether the operation returns the new revision.

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?

It is a single efficient sentence with the mutation and the revision requirement front-loaded, and it contains no filler. Its brevity is close to the point of under-specification rather than verbosity.

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

Completeness2/5

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

For a mutation tool with four required parameters, no schema descriptions, and no output schema, the definition does little to cover its behavior. It omits conflict handling, the idempotency role of requestId, and the return value, which leaves too much for an agent to infer.

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 description coverage is 0%, so the description must carry the parameter meaning, and it partially does: 'current contact revision' explains why revision matters, and 'clear' implies that date=null is allowed. The id and requestId parameters, along with the conflict behavior of revision, are left entirely unexplained.

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 gives a specific verb pair, 'set or clear,' and a specific resource, the contact's follow-up date. An agent can distinguish this write operation from the read-only sibling get_contact_follow_up_summary, but the description never names that sibling or says how the two differ.

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?

There is no explicit when-to-use or when-not-to-use guidance, no prerequisite described, and no interaction with related tools such as get_contact_follow_up_summary. The only implied guidance is that the operation applies to a single contact's follow-up date.

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