Skip to main content
Glama
Sign In

CallMCP — Phone Call MCP Server

by ai.callmcp
OverviewDiscussionsAdmin

Archive Agency Offer

agency_offer_archive
DestructiveIdempotent

Archives an offer so it can no longer be published or used for new enrollments. Requires an agency owner or admin and the current offer revision. Existing installations are not removed.

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>"
    },
    "name": "agency_offer_archive"
  }
}

Input Schema

NameRequiredDescriptionDefault
offerIdYesThe offer to archive.
partnerIdYesThe agency (partner) workspace ID.
expectedRevisionYesThe offer revision you last read.

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

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description goes further by naming exactly what stops working (publishing, new enrollments) and what is explicitly preserved (existing installations). It also discloses the authorization requirement, which annotations cannot express.

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 short sentences, front-loaded with the effect, then prerequisites, then the non-effect caveat. No filler and nothing repeated from the schema or annotations.

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 low-complexity single-operation mutation with rich annotations, a full input schema, and an output schema, nothing essential is missing: role requirement, revision precondition, and the blast radius are all covered.

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% and the schema already documents all three fields, so baseline is 3. 'Requires ... the current offer revision' hints at an optimistic-concurrency guard on expectedRevision, but the description does not state what happens on a stale revision, so added meaning is marginal.

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 ('Archives an offer') plus the concrete effect: it can no longer be published or used for new enrollments. The added scope note that existing installations survive cleanly separates this from the publish/save siblings without naming them.

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 invoking it — agency owner/admin role and the current offer revision — so an agent knows whether it can call it at all. It stops short of explicitly contrasting archive with save, publish, or preview, so the choice among siblings is left implicit.

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