Fulcra MCP Server

Set Contact Status

set_contact_status

Destructive

Set a peer-visible shared status on your own Event connection to signal whether a peer needs attention, requiring shared-status permission and complete scoped reads.

Instructions

Save a peer-visible Status pill on your own Event connection, only with share_contact_status enabled and complete scoped reads. Describe shared facts; never clear on incomplete history or treat an ack as a resolved decision. Failure must not block other work; never retry denial.

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": {
      "data_type": "<data_type>",
      "peer_userid": "<peer_userid>",
      "attention": "<attention>",
      "reason": "<reason>"
    },
    "name": "set_contact_status"
  }
}

Input Schema

Name	Required	Description
`reason`	Yes	Shared-status label; trimmed single-line Unicode, 1..80 code points, no controls.
`attention`	Yes	Whether the user needs to attend to this conversation.
`data_type`	Yes	Owned Event/<uuid> channel.
`peer_userid`	Yes	Exact UUID of its sole directly authorized peer.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.18.7Oct 23, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond the destructiveHint=true and idempotentHint=false annotations, the description discloses useful behavioral constraints: the status is peer-visible, writes require complete scoped reads, failures must not block other work, and denials must not be retried. It does not contradict the annotations.

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?

The description is very compact and front-loads the core action and precondition. Some phrasing is dense and slightly cryptic, but there is little wasted text.

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?

With rich schema descriptions, an output schema, and annotations covering safety, the description supplies the key operational preconditions and failure-handling rules. It is largely complete, though it could better distinguish sibling tools and explain the status lifecycle.

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 100%, so all four parameters are already documented in the schema. The description adds conceptual context like shared facts and acknowledgements, but it does not add syntax or field-level meaning beyond the schema.

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 write action, 'Save a peer-visible Status pill,' and scopes it to the user's own Event connection. It is clearer than the title alone, but it does not explicitly distinguish this from related contact/status tools such as set_contact_identifier or set_contact_preferences.

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

Usage Guidelines4/5

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

It provides explicit preconditions: share_contact_status must be enabled and scoped reads must be complete. It also gives when-not guidance such as never clearing on incomplete history and never retrying denial, though it does not name alternative sibling tools.

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

Deploy Server