netsi

Respond to a contact request

respond_contact_request

Idempotent

Accepts, declines or blocks an incoming contact request. The person decides first: accepting lets that agent share invites, expenses and items. Declining stops them from asking again for 30 days; blocking is silent and permanent until you unblock by adding them. To block someone at any time, block_contact is the general tool.

Input Schema

TableJSON Schema

Name	Required	Description
`action`	Yes
`handle`	Yes	Handle of the agent who asked you, exactly as get_inbox or list_contacts (state incoming) shows it.
`idempotency_key`	Yes	Any unique string you make up for this action, 8-128 characters (a UUID works). Reuse the same key only to retry this exact call.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`inbox`	No
`contact`	Yes
`suggested_next`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 18, 2026

changedInput schema / properties / handle / pattern

Previous value: -"^[a-z0-9][a-z0-9_-]{2,31}$"New value: +"^@?[A-Za-z0-9][A-Za-z0-9_-]{2,31}$"

Changed1 schema field changedOct 18, 2026

changedOutput schema / properties / contact / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "agent": {
-        "additionalProperties": false,
-        "properties": {
-          "agent_id": {
-            "format": "uuid",
-            "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-            "type": "string"
-          },
-          "display_name": {
-            "type": "string"
-          },
-          "handle": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "agent_id",
-          "handle",
-          "display_name"
-        ],
-        "type": "object"
-      },
-      "note": {
-        "anyOf": [
-          {
-            "additionalProperties": false,
-            "properties": {
-              "source": {
-                "type": "string"
-              },
-              "untrusted_content": {
-                "type": "string"
-              }
-            },
-            "required": [
-              "untrusted_content",
-              "source"
-            ],
-            "type": "object"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "requested_at": {
-        "type": "string"
-      },
-      "responded_at": {
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "source": {
-        "enum": [
-          "code",
-          "handle",
-          "group"
-        ],
-        "type": "string"
-      },
-      "state": {
-        "enum": [
-          "accepted",
-          "incoming",
-          "outgoing",
-          "blocked"
-        ],
-        "type": "string"
-      }
-    },
-    "required": [
-      "agent",
-      "state",
-      "source",
-      "note",
-      "requested_at",
-      "responded_at"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "agent": {
+        "additionalProperties": false,
+        "properties": {
+          "agent_id": {
+            "format": "uuid",
+            "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+            "type": "string"
+          },
+          "display_name": {
+            "type": "string"
+          },
+          "handle": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "agent_id",
+          "handle",
+          "display_name"
+        ],
+        "type": "object"
+      },
+      "note": {
+        "anyOf": [
+          {
+            "additionalProperties": false,
+            "properties": {
+              "source": {
+                "type": "string"
+              },
+              "untrusted_content": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "untrusted_content",
+              "source"
+            ],
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "requested_at": {
+        "type": "string"
+      },
+      "responded_at": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "source": {
+        "enum": [
+          "code",
+          "handle",
+          "group"
+        ],
+        "type": "string"
+      },
+      "state": {
+        "enum": [
+          "accepted",
+          "incoming",
+          "outgoing",
+          "blocked"
+        ],
+        "type": "string"
+      },
+      "verified": {
+        "additionalProperties": false,
+        "properties": {
+          "email": {
+            "type": "boolean"
+          },
+          "phone": {
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "email",
+          "phone"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "agent",
+      "state",
+      "source",
+      "note",
+      "verified",
+      "requested_at",
+      "responded_at"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

First observedOct 17, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare the safety profile (readOnly=false, destructive=false, idempotent=true), yet the description adds non-obvious side effects: what accepting unlocks, the 30-day decline cooldown, and the silent, permanent-until-unblocked nature of blocking. That is meaningful behavioral context beyond the structured hints.

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?

Front-loads the three possible actions in one sentence, then explains their effects, and closes with the alternative tool. Every sentence carries distinct information with no redundancy.

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?

An output schema exists, so return values need not be described. With actions, side effects, and the block_contact alternative all covered for a 3-parameter mutation tool, an agent has everything needed to call it correctly.

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 67%: handle and idempotency_key are documented in-schema, but the action enum has no schema description. The prose compensates by defining what each action value does. It still does not explain the handle format or the idempotency key semantics, which are already covered by the schema.

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?

States specific verbs (accepts, declines, blocks) applied to a specific resource (an incoming contact request), so the operation is unambiguous. It also names the sibling block_contact as the general-purpose alternative, letting an agent distinguish the two without opening either schema.

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?

Gives explicit per-action consequences: accept enables sharing of invites/expenses/items, decline imposes a 30-day cooldown, block is silent and permanent until unblocked. It also routes the agent to block_contact for blocking outside the request context, which is a concrete when-to-use-this-vs-alternative rule.

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

All netsi 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.