voicehook

Add an activity line

activity

Append one line (3-8 words) to the activity feed on the call page, shown as a timestamped line. Never spoken. context and faq: hidden background of this line for the voicebot.

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": {
      "session": "<session>",
      "text": "<text>"
    },
    "name": "activity"
  }
}

Input Schema

Name	Required	Description
`faq`	No	Up to 3 likely follow-up questions with prepared answers [{q, a}] (max 200 chars each), hidden, for the voicebot.
`goal`	No	Optional goal of this entry: number or title of a goal of the account (0 or empty = no goal). Unknown goals are ignored. Without it the entry inherits the goal of your last status (helpers: no inheriting).
`text`	Yes	3-8 words.
`context`	No	Hidden background of this entry for the voicebot (what, why, current state), max 2000 chars, never shown on the page.
`session`	Yes	The `session` value returned by join.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

addedInput schema / properties / goal

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional goal of this entry: number or title of a goal of the account (0 or empty = no goal). Unknown goals are ignored. Without it the entry inherits the goal of your last status (helpers: no inheriting).",
+  "title": "Goal"
+}

Changed3 schema fields changedOct 20, 2026

addedInput schema / $defs

Added value: +{
+  "FaqPair": {
+    "properties": {
+      "a": {
+        "description": "The prepared answer, max 200 chars.",
+        "title": "A",
+        "type": "string"
+      },
+      "q": {
+        "description": "A likely follow-up question of the person, max 200 chars.",
+        "title": "Q",
+        "type": "string"
+      }
+    },
+    "required": [
+      "q",
+      "a"
+    ],
+    "title": "FaqPair",
+    "type": "object"
+  }
+}

addedInput schema / properties / context

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Hidden background of this entry for the voicebot (what, why, current state), max 2000 chars, never shown on the page.",
+  "title": "Context"
+}

addedInput schema / properties / faq

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "$ref": "#/$defs/FaqPair"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Up to 3 likely follow-up questions with prepared answers [{q, a}] (max 200 chars each), hidden, for the voicebot.",
+  "title": "Faq"
+}

First observedOct 17, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover mutability and open-world behavior, and the description adds genuinely new context: the line is appended, timestamped, visible on the call page, and never spoken, while context/faq remain hidden from the page. It does not mention that repeated calls create duplicate lines (consistent with idempotentHint=false) or the permission/session prerequisites.

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?

Three short sentences, front-loaded with the action and the visible result, followed by the key behavioral constraint and the hidden-field note. No filler; the fragment 'Never spoken.' earns its place as the main routing signal.

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?

All five parameters are documented in-schema, an output schema exists, and annotations cover the safety profile, so the description only needs to add the visible/hidden distinction, which it does. The remaining gap is the session prerequisite ('the `session` value returned by join') being left entirely to the schema.

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 the baseline is 3. The description only re-frames `context` and `faq` as 'hidden background of this line for the voicebot', which is essentially what the schema already documents; no extra syntax, format, or selection guidance is added.

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?

States a specific verb and resource ('Append one line ... to the activity feed on the call page') plus a hard length constraint (3-8 words). It implicitly separates itself from the speaking siblings via 'Never spoken', but never names `say` or `helper_activity`, so the differentiation is inferred rather than explicit.

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 'Never spoken' and 'shown as a timestamped line' phrasing implies this is for silent page log entries rather than spoken output, which does route the agent away from `say`. However there is no explicit when-to-use/when-not statement, no mention that a session from `join` must exist, and no guidance on choosing this over `helper_activity`.

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

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