Skip to main content
Glama
Sign In

Widely

by com.widely-mobile
OverviewDiscussionsAdmin

Find shared chats

search_shared_chats
Read-onlyIdempotent

Finds chats on this seat shared with one person. Set one of contact_id, user_id, or number. contact_id is a saved contact. user_id is the other person's Widely user. A number matches that phone number, including a national form of the same number. Returns one page of chats with the chat name and the last message. limit and offset are the page that was applied, and total is the full match count.

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

Input Schema

NameRequiredDescriptionDefault
limitNoChats in this page. Default 10, maximum 25.
numberNoPhone number, including a national form of the same number. Set this, or contact_id, or user_id.
offsetNoChats to skip before this page. The following page starts at offset plus count.
user_idNoWidely user id of the other person. Set this, or contact_id, or number.
contact_idNoSaved contact id. Set this, or user_id, or number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds meaningful behavioral context beyond annotations: it explains the return shape (chat name and last message) and pagination semantics (limit, offset, total).

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?

The description is a compact, front-loaded paragraph with zero waste. Each sentence carries useful information: scope, parameter selection rules, number matching, return shape, and pagination meaning.

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 5-parameter tool with no output schema, the description adequately covers the selection criteria, return fields, and pagination. It leaves minor gaps such as default limit behavior (deferred to schema) but is otherwise complete for correct invocation.

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 description coverage is 100%, so the baseline is 3. The description adds value beyond the schema by clarifying that a number matches the phone number including its national form, and by explaining that limit/offset represent the applied page while total is the full match count.

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?

The description states a specific verb ("Finds") and resource ("chats") with a clear scope ("on this seat shared with one person"). It clearly distinguishes the tool from generic message or contact search, though it does not explicitly name sibling alternatives.

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 description implies usage by stating "shared with one person" and requiring one of contact_id, user_id, or number. However, it does not explicitly say when to use this tool versus search_messages, search_contacts, or get_thread, nor does it provide exclusions.

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

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

Resources