Skip to main content
Glama
Sign In

CallMCP — Phone Call MCP Server

by ai.callmcp
OverviewDiscussionsAdmin

Publish Agency Offer

agency_offer_publish
Idempotent

Publishes the previewed offer as a new immutable version and returns its enrollment link. Requires an agency owner or admin, plus the fingerprint and revision from preview; partner-billed offers also need billing collection to be ready. Publishing the same fingerprint again returns the existing version.

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>",
      "offerId": "<offerId>",
      "expectedRevision": "<expectedRevision>",
      "fingerprint": "<fingerprint>"
    },
    "name": "agency_offer_publish"
  }
}

Input Schema

NameRequiredDescriptionDefault
offerIdYesThe offer to publish.
partnerIdYesThe agency (partner) workspace ID.
fingerprintYesThe manifest fingerprint returned by preview.
expectedRevisionYesThe draft revision returned by preview.

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.7/5.0
Behavior5/5

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

Goes well beyond the annotations by explaining how idempotency works (keyed on fingerprint — a repeat returns the existing version), that the result is an immutable new version, that an owner/admin role is required, and that partner-billed offers have a billing-collection prerequisite. The destructiveHint=false claim is reinforced by the 'new immutable version' framing rather than contradicted.

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 tight sentences: what it does and returns first, then prerequisites, then the repeat-call behavior. No filler, and the most important outcome is front-loaded.

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?

For a mutation tool with an output schema already covering the return payload, the description supplies everything else an agent needs: authorization requirement, prerequisite billing state, the preview-sourced inputs, and duplicate-call behavior.

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, but the description adds real semantics: fingerprint and expectedRevision are the values obtained from preview, and the fingerprint doubles as the idempotency key. That meaning is not present in the schema descriptions, which only say where the fields come from.

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 ('Publishes the previewed offer as a new immutable version') and pairs it with a concrete outcome ('returns its enrollment link'). The reference to the 'previewed' offer distinguishes it from agency_offer_preview and agency_offer_save without ambiguity.

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?

Clear context: it must be called on an offer that has already been previewed, with the fingerprint and revision produced by preview, and only by an owner/admin. No explicit exclusions are given (e.g., why not archive or save instead), which keeps it just below a 5.

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