Skip to main content
Glama

propose_to_family

Sends a prepared, user-approved proposal preview to the family for approval in Telegram using only its draftId. Call it after the user confirms the exact preview.

Instructions

Sends to the family for approval in Telegram the proposal preview_proposal prepared, exactly as previewed: pass only its draftId, and only after the user said yes to this exact preview. The card's own texts were checked at the preview (name it without numbers, not even spelled out — 'a new phone', not 'iPhone 15'; 'the family car', not a model number; the server prints every number on the card). The server checks the draft again: advisor.draft_stale means the family's numbers, the voters or the language changed since the preview, advisor.draft_not_found that the draft expired (30 minutes), was sent already or is a revision's (send that with revise_proposal): prepare a new preview, show it, and ask for yes again. advisor.too_many_open means the user already has 5 proposals waiting: one must be decided or withdrawn first. Without a draftId the answer is advisor.preview_required.

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": {
      "draftId": "<draftId>"
    },
    "name": "propose_to_family"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftIdYesThe draftId preview_proposal answered for the card the user said yes to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, so the description carries the real burden and does: it discloses server-side re-validation, the 30-minute draft expiry, the 5-open-proposal cap, and the meaning of advisor.draft_stale, advisor.draft_not_found, advisor.too_many_open and advisor.preview_required. That is far beyond what the single annotation provides.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and the precondition, and every clause carries operational information (number-formatting rule, error codes, limits). It is dense and somewhat run-on with parenthetical asides, which costs a point but nothing is truly wasted.

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 one-parameter mutation with no output schema, the description covers prerequisites, the exact value to pass, failure modes with recovery actions, and quota limits. An agent has everything needed to call it correctly and to handle errors.

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% and the single parameter is already documented, so the baseline is 3; the description adds genuine meaning by constraining draftId to the value preview_proposal returned for the exact card the user approved, and by stating that omitting it yields advisor.preview_required.

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 ('Sends to the family for approval in Telegram the proposal preview_proposal prepared') and ties it to the sibling that produces its input, so an agent can distinguish it from preview_proposal and revise_proposal without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives an explicit precondition ('only after the user said yes to this exact preview') and names the alternative path for revisions ('send that with revise_proposal'), plus the recovery flow of re-previewing and re-asking. When-to-use and when-not-to-use are both covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.