CallMCP — Phone Call MCP Server

Invite Agency Team Member

agency_profile_invite

Creates a staff invitation for an email address with the admin, operator or reader role and returns a one-time invite link that expires in 7 days. Requires an agency owner or admin; only the owner can invite an admin. It sends no email; the returned link is delivered by whoever created the invite.

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>",
      "email": "<email>",
      "role": "<role>"
    },
    "name": "agency_profile_invite"
  }
}

Input Schema

Name	Required	Description
`role`	Yes	Role granted on acceptance: admin, operator or reader.
`email`	Yes	Email address the invitee must sign in with (verified).
`partnerId`	Yes	The agency (partner) workspace ID.

Output Schema

Name	Required	Description
`error`	No	Present when success is false
`receipt`	No
`success`	Yes	Whether the tool completed successfully

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already mark this as a non-read-only, non-destructive, non-idempotent, non-open-world operation. The description adds real value on top: the 7-day expiry, the one-time nature of the link, the absence of an outbound email, and the authorization tiers. It does not say what happens on a duplicate invite for the same address, which is the main open behavioral question.

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, front-loaded with what the tool creates and returns, then constraints. No filler and nothing that restates the name or title.

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?

An output schema exists, yet the description still usefully summarizes the return value (one-time link, 7-day expiry) and how it reaches the invitee. For a non-idempotent mutation with only three parameters this is nearly complete; only re-invite/duplicate handling is unaddressed.

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 coverage is 100%, so the baseline is 3; the description earns an extra point by tying the role enum to the privilege rule (owner-only for admin), which is meaning the schema does not encode. Email and partnerId semantics are left to the schema, which already documents them.

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 ('Creates a staff invitation for an email address') plus the notable side effect — returns a one-time invite link valid 7 days. The invite-creation action is clearly separable from the revoke/accept siblings, though no sibling is named explicitly.

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 clear preconditions for use: caller must be an agency owner or admin, and only the owner may invite an admin. It also clarifies the delivery model ('sends no email'). It stops short of telling the agent what to do instead when the precondition fails or when an invite already exists.

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