Call Me

Set thread title

set_thread_title

DestructiveIdempotent

Name this session's conversation thread on the human's phone (e.g. the project or task you are working on). Shown as the thread title in the app.

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_token": "<session_token>",
      "title": "<title>"
    },
    "name": "set_thread_title"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes	A short name, 3 to 5 words, e.g. "Deploy of billing API".
`session_token`	Yes	The session_token from an earlier result. It keeps every call and text in one thread on their phone.

Output Schema

Name	Required	Description	Default
`ok`	Yes	True when the title was saved.
`label`	Yes	The title as it now shows on the phone.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 4, 2026

addedInput schema / properties / session_token / description

Added value: +"The session_token from an earlier result. It keeps every call and text in one thread on their phone."

addedInput schema / properties / title / description

Added value: +"A short name, 3 to 5 words, e.g. \"Deploy of billing API\"."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "label": {
+      "description": "The title as it now shows on the phone.",
+      "title": "Label",
+      "type": "string"
+    },
+    "ok": {
+      "description": "True when the title was saved.",
+      "title": "Ok",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ok",
+    "label"
+  ],
+  "title": "TitleResult",
+  "type": "object"
+}

First observedOct 4, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is partly covered. The description usefully adds that the value surfaces visibly to the human on their phone, but never says whether an existing title is overwritten — the most important behavior given destructiveHint.

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?

Two short sentences, front-loaded with the action and its effect. The second sentence largely restates the title/thread naming already implied, making it near-redundant rather than earning full marks.

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?

An output schema exists and annotations cover idempotency and destructiveness, so the description needn't explain returns. For a simple two-parameter tool it is nearly complete, with only the overwrite behavior and timing of the call left unstated.

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 coverage is 100%, with both parameters fully documented including the 3-to-5-word constraint and an example. The description only adds the framing of what the title should describe, which slightly reinforces the schema rather than extending it.

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 ("Name") and a specific resource ("this session's conversation thread") plus the observable effect ("shown as the thread title in the app"). It is clearly distinct from siblings like say, text, and call, though the distinction is inferred from the resource rather than stated.

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 parenthetical "e.g. the project or task you are working on" implies what content belongs here, but there is no explicit guidance on when to call it (e.g. once at session start) or when not to, and no mention of alternatives or prerequisites.

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

All Call Me 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.