Call Me

Set up Call Me

setup

Read-onlyIdempotent

Return first-setup instructions and clickable App Store and Google Play download links, for when you do not have the human's Call Me number yet. Show both links to the human as clickable links, then ask them to open My Number in the app and give you its 10 digits. Nothing is sent and nothing rings.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "setup"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`status`	Yes	"setup_required": no Call Me number is known yet.
`message`	Yes	What to tell the human, with both download links.
`storage`	No	How the number is stored.
`app_store_url`	Yes	Call Me on the App Store, for iPhone.
`play_store_url`	Yes	Call Me on Google Play, for Android.
`local_config_key`	No	The key that holds it in that file.
`local_config_path`	No	Where a local client keeps the number.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 4, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "app_store_url": {
+      "description": "Call Me on the App Store, for iPhone.",
+      "title": "App Store Url",
+      "type": "string"
+    },
+    "local_config_key": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "The key that holds it in that file.",
+      "title": "Local Config Key"
+    },
+    "local_config_path": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Where a local client keeps the number.",
+      "title": "Local Config Path"
+    },
+    "message": {
+      "description": "What to tell the human, with both download links.",
+      "title": "Message",
+      "type": "string"
+    },
+    "play_store_url": {
+      "description": "Call Me on Google Play, for Android.",
+      "title": "Play Store Url",
+      "type": "string"
+    },
+    "status": {
+      "description": "\"setup_required\": no Call Me number is known yet.",
+      "title": "Status",
+      "type": "string"
+    },
+    "storage": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "How the number is stored.",
+      "title": "Storage"
+    }
+  },
+  "required": [
+    "status",
+    "app_store_url",
+    "play_store_url",
+    "message"
+  ],
+  "title": "SetupResult",
+  "type": "object"
+}

First observedOct 4, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered upstream. The description adds meaningful context beyond that — 'Nothing is sent and nothing rings' clarifies that invoking it causes no call or message, and it prescribes the human-facing interaction (show links as clickable, then request the number). Return format is left to the output schema.

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 condition for use is front-loaded in the first sentence, followed by the actionable steps and a closing reassurance. Wording like 'Show both links to the human as clickable links' is slightly redundant but each sentence carries operational value; nothing is bloated.

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 zero-argument, read-only setup tool with an output schema covering return values, the description supplies purpose, trigger condition, and the exact human interaction sequence. Only the explicit hand-off to the calling tools after the number is obtained is missing.

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?

The tool takes zero parameters, so the baseline is 4 and there is no parameter meaning the description needs to compensate for. The description correctly says nothing about inputs, matching the empty 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?

The description names a specific action and resource — returning first-setup instructions plus clickable App Store and Google Play download links — and states the exact condition that selects it: when the agent does not yet have the human's Call Me number. That condition also separates it from siblings like call or text, which require the number, so an agent can pick it without opening any schema.

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 gives a clear when-to-use condition ('for when you do not have the human's Call Me number yet') plus the follow-up step of asking for the 10-digit number from My Number in the app. It does not explicitly name the alternative tool to use once the number is known, so it stops short of full routing guidance.

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.