Cleat

Wait for a code

wait_for_code

Waits for the next verification code to arrive at a line and returns it. Call this immediately BEFORE triggering the text, so nothing is missed. Returns timedOut: true if none arrives in time.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lineId": "<lineId>"
    },
    "name": "wait_for_code"
  }
}

Input Schema

Name	Required	Description
`from`	No	Optional. Only consider messages whose sender contains this text, case-insensitively — a short code, say 32665.
`lineId`	Yes	The line's id, from list_lines.
`service`	No	Optional. Only consider messages Cleat attributed to this service (its id or name, e.g. facebook), or that carry this label from your workspace's contacts.
`timeoutSeconds`	No	How long to wait, up to 55. Defaults to 30.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 23, 2026

addedInput schema / properties / from

Added value: +{
+  "description": "Optional. Only consider messages whose sender contains this text, case-insensitively — a short code, say 32665.",
+  "type": "string"
+}

addedInput schema / properties / service

Added value: +{
+  "description": "Optional. Only consider messages Cleat attributed to this service (its id or name, e.g. facebook), or that carry this label from your workspace's contacts.",
+  "type": "string"
+}

First observedSep 12, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the blocking/waiting behavior, the timeout result, and the timing requirement. It doesn't mention potential side effects or rate limits, but for a read/wait operation this is reasonably transparent.

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?

Three sentences, each earning its place: what it does, when to call it, and what the timeout result is. The most important usage guidance is front-loaded.

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 waiting tool with no output schema, the description covers the key behavioral aspects: blocking, timeout, and timing. It could mention what the return value looks like on success, but the core usage is clear. The sibling context (latest_code) suggests an alternative for non-waiting retrieval, which is adequately implied.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all four parameters. The description adds the crucial timing context ('immediately BEFORE triggering the text') and the timeout return behavior, but doesn't add much beyond the schema for individual parameters. Baseline 3 is appropriate.

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 states a specific verb ('waits'), a specific resource ('verification code'), and a clear outcome ('returns it'). It also distinguishes itself from siblings by emphasizing the waiting behavior and the timing instruction ('immediately BEFORE triggering the text').

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?

The description explicitly tells the agent when to call this tool ('immediately BEFORE triggering the text') and what to expect ('Returns timedOut: true if none arrives in time'). It also implies the alternative (latest_code) by focusing on waiting for a future code rather than fetching the latest existing one.

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

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

Resources

Need Help?