Desk keeps a support team’s approved answers, refund rules, and escalation limits, then lets an assistant read that policy before it replies. A 14-day trial, then Pro. The price is only at checkout.
Scored across 13 tools
Each tool targets a distinct resource and action (desk, answer, commitment, escalation limit, refund rule) with clear verbs. evaluate_commitment vs evaluate_escalation are parallel but the descriptions sharply distinguish exact wording approval from channel escalation permission. Minor overlap exists where get_desk_context bundles answers plus the lists that search_approved_answers and list_* also retrieve, but the read patterns remain separable.
All tools follow a predictable verb_noun snake_case pattern: create_*, get_*, list_*, save_*, evaluate_*, search_*. Singular/plural usage (save_approved_answer vs search_approved_answers) reflects singular-write vs plural-read semantics rather than inconsistency.
13 tools is well-scoped for a policy-management domain, with coherent list/save pairs across four resource types plus a few read/evaluate tools. Every tool earns its place and none seems redundant.
The surface covers the core lifecycle: create/list desks, save/list answers, commitments, escalation limits, and refund rules, plus evaluate and search. Gaps are minor: no explicit delete/retire or update operations for desks and non-answer resources, though save-with-revision partially covers updates.
Create a support desk when the user asks for a new policy home. Does not approve answers, refunds, features, or timelines.
Inputs: name (required), description. Returns: data
Decide whether a proposed refund, feature, or timeline is in the approved set. REFUSED means do not say it, do not invent a substitute, and draft for human review instead of promising the customer. APPROVED means sayOnly is the only permitted wording. Pass channel to also enforce the escalation limit.
Inputs: kind (required), deskId (required), proposal (required), channel. Returns: data
Decide whether this channel may escalate or may promise a refund, feature, or timeline. REFUSED means do not escalate, do not invent a tier, and draft for human review instead of promising the customer. Permission to promise still requires evaluate_commitment for the exact wording.
Inputs: action (required), deskId (required), channel (required), targetTier. Returns: data
Retrieve selected approved answers for a customer question, plus the desk's approved refund rules, commitments, and escalation limits. This is evidence, not permission. A missing or RETIRED answer is not an invitation to invent one. Call evaluate_commitment before promising a refund, feature, or timeline. If tools fail or return gaps or REFUSED, draft for human review instead of promising the customer.
Inputs: deskId (required), question (required), limit. Returns: data
Read approved feature and timeline statements. Listing them does not approve a different promise. Call evaluate_commitment with the exact wording before saying one.
Inputs: deskId (required), kind, includeRetired. Returns: data
Read escalation limits. A channel with no APPROVED limit cannot promise a refund, feature, or timeline and cannot be given an invented escalation path.
Inputs: deskId (required), includeRetired. Returns: data
Read refund rules on a desk. Only APPROVED rules can authorize wording, and only through evaluate_commitment. Do not treat this list as permission to invent a refund.
Inputs: deskId (required), includeRetired. Returns: data
List this team's support desks. Use the returned id. Do not guess a desk.
Inputs: offset. Returns: data
Store or revise an answer the user has explicitly approved. Identical retries keep the same revision. A changed answer requires expectedRevision from a previous read.
Inputs: topic (required), answer (required), deskId (required), question (required), +2 more. Returns: data
Store a feature or timeline statement the user has explicitly approved. The statement is the only wording that can later pass evaluate_commitment. Do not save a date or a feature the user did not approve.
Inputs: kind (required), name (required), deskId (required), statement (required), +2 more. Returns: data
Store the escalation limit the user has explicitly approved for one channel. maxTier must be on tierLadder. Promise flags default closed unless the user sets them true. A limit does not itself approve refund, feature, or timeline wording.
Inputs: name (required), deskId (required), channel (required), maxTier (required), +7 more. Returns: data
Store a refund rule the user has explicitly approved. matchTerms must name a specific situation. The word refund alone is not a rule. remedy is the only wording that may later be approved. decision ALLOW grants that wording. decision DENY refuses a refund and records the denial script.
Inputs: name (required), deskId (required), remedy (required), decision (required), +4 more. Returns: data
Look up approved answers by topic, question, or answer text. An empty result means there is no approved answer. Draft for human review; do not invent one or promise the customer. Page with offset.
Inputs: deskId (required), query, offset, includeRetired. Returns: data
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.