Skip to main content
Glama
Sign In

CallForMe

by tel.callforme
OverviewDiscussionsAdmin

Wait for the user to finish setup

wait_for_setup
DestructiveIdempotent

After place_call returned needs_setup and the user has SEEN the link: wait for them to finish it. If your client only shows your reply when your turn ends (ChatGPT), end your turn with the link first and call this after the user replies. Returns as soon as they're done and places the call right then (status "calling" with call_id, and account_key to save), so the user never has to say "done". Waits up to wait_seconds (max 50). If it returns status "waiting_for_setup", call it again. Setup links expire after 24 hours.

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": {
      "setup_code": "<setup_code>"
    },
    "name": "wait_for_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
setup_codeYesThe setup_code from needs_setup, e.g. "QF6S-2U4Z"
account_keyNoOnly for clients without OAuth: the cfm_ API key (from the account page or an earlier setup). Leave out when connected with OAuth.
wait_secondsNoHow long to wait, max 50 (larger values are capped). Default 50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Despite a passive-sounding name, the description discloses that this is not a pure poll: it places the call on success and returns status "calling" with call_id and account_key to persist. That reconciles the surprising destructiveHint=true/openWorldHint=true annotations with the tool's apparent purpose, and it documents both possible return statuses plus the wait cap beyond what annotations 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-loaded with the trigger condition and the payoff, and every sentence carries operational information (turn-ending caveat, return statuses, retry rule, expiry). It is dense and slightly parenthetical, but nothing is filler.

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?

With no output schema, the description carries the full burden of explaining returns and does so: status "calling" plus call_id and account_key, and the "waiting_for_setup" retry state. For a 3-parameter async coordination tool, an agent has everything needed to invoke and loop correctly.

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 description coverage is 100%, so setup_code, account_key (OAuth vs cfm_ key), and wait_seconds (max 50) are already fully documented. The description only restates the wait cap and the origin of setup_code, adding no syntax, format, or constraint detail beyond the schema; 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?

States a specific verb and resource: waits for the user to finish setup, then places the call immediately. It is clearly distinguished from siblings by naming the precondition (place_call returned needs_setup) and the alternative outcome (call again on "waiting_for_setup"), so an agent can separate it from place_call and get_call without opening a schema.

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?

Explicit when-to-use is given (only after place_call returned needs_setup AND the user has SEEN the link), including a client-specific sequencing rule for ChatGPT where the turn must end before calling. It also states the re-invocation condition, the timeout cap, and the 24-hour link expiry — no inference required.

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

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