Skip to main content
Glama
Sign In

CallMCP — Phone Call MCP Server

by ai.callmcp
OverviewDiscussionsAdmin

Accept Agency Invitation

agency_profile_accept_invite
Idempotent

Joins the agency using the token from an invite link. The signed-in user must have a verified email that matches the invited address, and the invite must be unexpired and not revoked. Accepting the same invite again is a no-op.

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": {
      "partnerId": "<partnerId>",
      "token": "<token>"
    },
    "name": "agency_profile_accept_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesThe token from the invite link.
partnerIdYesThe agency (partner) workspace ID.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when success is false
receiptNo
successYesWhether the tool completed successfully

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?

Adds real context beyond the annotations: a verified-email authorization prerequisite and invite state constraints (unexpired, not revoked) that the annotation flags do not convey. The no-op-on-repeat note usefully interprets the idempotentHint, though it partly restates it. Error behavior and side effects on the user's account are not described.

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 compact sentences: purpose first, then preconditions, then idempotency. No filler and nothing redundant with the schema.

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?

With an output schema present and full param coverage, the description need not explain return values, and it covers purpose, authorization, and state preconditions. It is slightly thin on failure modes (what happens on email mismatch or revoked invite) for a mutation tool with openWorldHint=false.

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%, with both token and partnerId documented in the schema itself. The description echoes the token's origin (invite link) but adds no format, source, or constraint detail beyond what the schema already provides, so the baseline 3 applies.

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?

States a specific verb and resource: joins the agency using an invite-link token. Combined with the linked-invite framing, an agent can distinguish this acceptance flow from the sibling invite/revoke_invite tools without inspecting the schema. It stops short of explicitly naming those alternatives.

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 concrete gating conditions for use: the signed-in user must have a verified email matching the invited address, and the invite must be unexpired and unrevoked. That is clear context, though there is no explicit statement of when NOT to use it or which sibling to choose instead.

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

All CallMCP — Phone Call MCP Server 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