Skip to main content
Glama

set_pin

Protect your Signal account from SIM-swap attacks by setting a registration lock PIN. The PIN must be 4–20 digits.

Instructions

Set a Signal Registration Lock PIN to protect your account against SIM-swap and unauthorized re-registration. Once set, anyone attempting to re-register your phone number on Signal must provide this PIN. The PIN must be 4–20 digits. Signal also uses the PIN to derive your storage encryption key. If you forget the PIN, you must wait 7 days for the lock to expire before re-registering. Use when you want to harden your account against SIM-swap attacks. Use remove_pin to disable the lock. Do NOT set a PIN you might forget — losing it locks you out of your account for 7 days.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pinYes4–20 digit numeric PIN (e.g. '123456')
Behavior4/5

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

With no annotations, the description fully covers behavioral aspects: PIN used for encryption key derivation, 7-day lockout if forgotten. Could mention if changing PIN is possible, but adequate.

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?

Concise yet comprehensive: front-loaded with purpose, then details, usage, alternatives, and warning. No unnecessary sentences.

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?

All relevant context is provided: when to use, consequences, PIN format, alternative tool, warning. No output schema needed given the tool's simplicity.

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 describes PIN as 4-20 digit string; description adds that it derives encryption key and causes lockout if forgotten, enriching the parameter's significance.

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 clearly states the tool sets a Signal Registration Lock PIN to protect against SIM-swap attacks. It distinguishes from sibling tools like remove_pin.

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?

Explicitly says 'Use when you want to harden your account against SIM-swap attacks' and provides alternative remove_pin and a warning about forgetting the PIN.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/googlarz/signal-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server