openactors

Note that you chased

record-follow-up

Record follow-ups to prevent repeated flags for the same unresponsive leads. Tracks which URLs have been contacted, ensuring silence is not flagged again immediately.

Instructions

Records that you followed up, so the same silence is not flagged again immediately.

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": {
      "urls": "<urls>"
    },
    "name": "record-follow-up"
  }
}

Input Schema

Name	Required	Description	Default
`urls`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 5, 2026

TDQS

A3.9/5.0

Behavior4/5

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It clearly reveals that this is a state-changing operation and explains the observable consequence: the same silence will not be flagged again immediately. It does not mention idempotency or error handling, but the key side effect is disclosed.

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?

A single sentence communicates the action, target, and purpose with no wasted words. The most important information is front-loaded.

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 tool with one required array parameter and no output schema, the description is largely sufficient: it states what is recorded and why. The main gaps are the implicit meaning of the urls parameter and the lack of guidance about related tools, but these are minor given the tool's low complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema only provides the parameter name and type, and schema description coverage is 0%. The description never explicitly defines what 'urls' should contain, though context implies it is the list of followed-up URLs. This is only partial compensation for a completely undocumented parameter.

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?

The description uses a specific verb ('Records'), identifies the resource (follow-ups on URLs), and explains the intended outcome: preventing the same silence from being flagged again. This gives a clear sense of what the tool does and how it differs from query-oriented siblings like get-follow-ups or record-response.

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?

The description implies the right context: call it after you have followed up and want to suppress an immediate re-flag. However, it does not explicitly name alternatives or state when not to use it, so the usage guidance is only implicit.

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