Widely

Block a contact

block_contact

Idempotent

Blocks a person when the user asks you to block them, their number, or a saved contact. Calls and messages to that person are refused, and calls and messages from them are refused. This is the Widely app block list for this Widely user, on every number they use. Pass phone_number, contact_id, or both. contact_id is a saved contact from search_contacts. A number is stored the same way the app stores it. Blocking someone who is already blocked leaves that block as it is.

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": "block_contact"
  }
}

Input Schema

Name	Required	Description	Default
`contact_id`	No	Saved contact id. Blocks that contact's Widely user and saved numbers.
`phone_number`	No	Phone number to block. Pass this, contact_id, or both.

Output Schema

Name	Required	Description	Default
`status`	Yes	blocked when this call saved a block. already_blocked when each target was already blocked.
`blocked`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 12, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well past the annotations by describing the actual effect: calls and messages in both directions are refused, and the block applies account-wide to every number the user has. It also restates idempotency in operational terms ("Blocking someone who is already blocked leaves that block as it is") and notes the number is stored as the app stores it, all of which the annotations alone do not convey.

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?

Front-loads the block action and follows with effects, parameters, and the idempotent edge case in a logical order. Slightly redundant phrasing ("Calls and messages to that person are refused, and calls and messages from them are refused") could be compressed into one bidirectional statement.

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 two-parameter mutation with an output schema and full annotation coverage, the description supplies the effect, scope, input guidance, and idempotency needed to call it correctly. It could be marginally more complete by pointing to unblock_contact as the reversal path, since it only says a repeat block is a no-op.

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 100%, so the baseline is 3; the description earns an extra point by defining contact_id's provenance (a saved contact obtained from search_contacts) and by stating the either-or-both combination rule. Minor remaining gap: no format expectation for phone_number beyond "stored the same way the app stores it."

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 a specific verb and resource ("Blocks a person") and immediately bounds the scope to the Widely app block list for this user, across every number they use. The trigger condition ("when the user asks you to block them, their number, or a saved contact") lets an agent distinguish it from unblock_contact and search_contacts without opening another 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?

Gives an explicit use condition tied to user intent and clarifies the accepted inputs ("Pass phone_number, contact_id, or both"), plus the already-blocked no-op case. It stops short of naming unblock_contact as the counterpart tool or stating any exclusion, so routing away from this tool is still inferred.

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

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