CallMCP — Phone Call MCP Server

Opt Installation into Canary

agency_installation_opt_into_canary

Idempotent

Marks the client's installation as a canary, so it can receive package updates before other clients of the same agency. Requires the client owner and accepted set to true. It applies no update by itself.

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>",
      "installationId": "<installationId>",
      "expectedRevision": "<expectedRevision>",
      "accepted": "<accepted>"
    },
    "name": "agency_installation_opt_into_canary"
  }
}

Input Schema

Name	Required	Description
`accepted`	Yes	Must be true to confirm the owner opts in.
`partnerId`	Yes	The agency (partner) workspace ID.
`installationId`	Yes	The agency package installation to act on.
`expectedRevision`	Yes	The installation revision you last read. The call is rejected if the installation has changed since.

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

A3.7/5.0

Behavior3/5

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

Annotations already declare idempotent/non-destructive/non-read-only, and the description adds a genuine permission requirement (client owner) and a scope boundary ("applies no update by itself"). It does not mention the optimistic-concurrency rejection behavior or what happens to the installation's current update state, both of which matter for a mutation.

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?

Two tight sentences: the definition and effect come first, the precondition and scope caveat second. No filler, no repetition of the 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?

All four parameters are required and fully documented, an output schema exists, and the description covers who may call it and what it does not do. Only the failure/conflict path and any reversal path are left implicit, which is a minor gap for this complexity.

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's note that the owner must confirm links the const `accepted` flag to a real actor rather than a bare boolean, adding modest meaning. It says nothing extra about `expectedRevision` or the ID parameters.

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 ("Marks the client's installation as a canary") and explains the resulting effect (receives updates before other clients). The closing clause "It applies no update by itself" implicitly separates it from the apply-update sibling, though no alternative 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a precondition ("Requires the client owner and accepted set to true") and context for why one would opt in, but never states when to choose this over alternatives such as applying, previewing, or offboarding an update, nor any when-not-to guidance.

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.