Skip to main content
Glama
Sign In

Latchbell

by com.latchbell
OverviewDiscussionsAdmin

Phones that text for the business

text_phones
Read-only

Owners only (needs sign-in): The phones and Macs paired to text for the business (pair_phone). texts_go_out_from_this marks the one the business’s AI agent texts from (the most recently seen). can_text false: pair one first (pair_phone).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, non-destructive, closed operation. The description adds useful behavior context: sign-in requirement, the meaning of texts_go_out_from_this, and the pairing prerequisite indicated by can_text false.

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 description is short and front-loads the owner/sign-in restriction. However, the parenthetical use of pair_phone and terse camelCase field references make it slightly dense and less immediately readable.

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-parameter, read-only tool with annotations and no output schema, the description covers the main missing context: authentication, paired-device semantics, the active AI texting device, and the fallback to pair_phone. It is complete enough to call correctly, though the terse field wording could be clearer.

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 has zero parameters, so schema coverage is not a concern. The description does not need to explain parameter semantics, and it uses the space to explain important returned-field concepts instead.

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 identifies the resource clearly: phones and Macs paired to text for the business. It does not explicitly say it lists or returns them, but the noun phrase and title make the purpose understandable.

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 clear prerequisites: owners only and sign-in required. It also names the alternative action when can_text is false, explicitly directing the agent to pair_phone first.

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

All Latchbell 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