Skip to main content
Glama
Offorte Proposal Software

Offorte Proposal Software

Official
by offorte

send_proposal

Destructive

Sends a proposal to its assigned contacts via Offorte or your own delivery method, with optional message, password reset, and sender message ID.

Instructions

Send a proposal to its assigned contacts

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": {
      "proposal_id": "<proposal_id>"
    },
    "name": "send_proposal"
  }
}

Input Schema

NameRequiredDescriptionDefault
proposal_idYes
send_methodNoofforte
send_messageNo
password_resetNo
send_message_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.1
  2. Removed
  3. Changed2 schema fields changedv1.0.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  4. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the agent knows this is an irreversible outward-facing action. The description adds nothing beyond that: it does not explain that delivery happens by email, that a resend creates a duplicate send, or what send_method 'offorte' versus 'self' actually changes about the behavior.

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

Conciseness3/5

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

It is a single short sentence with no wasted words and the core action is front-loaded. However, that conciseness comes at the cost of under-specification rather than efficiency, so it cannot score higher.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a destructive, non-idempotent, open-world mutation with five parameters, no output schema, and no parameter documentation. The description supplies none of the prerequisites, delivery semantics, or parameter meaning an agent needs to invoke it safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, so the description must carry the meaning and it carries none. It never explains proposal_id, the offorte/self enum, send_message, send_message_id (likely a template reference), or password_reset — all of which materially change what gets sent.

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?

The description gives a specific verb ('Send') and resource ('a proposal') plus the recipient scope ('its assigned contacts'), so an agent can tell this is a delivery action rather than a read. It does not differentiate itself from any sibling (e.g., get_proposal_details or update_proposal_pricetables), leaving that to inference from the names.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool, what preconditions must hold (e.g., the proposal must exist and be in a sendable state), or what to do instead. The only implicit signal is that recipients come from the proposal's assigned contacts, but the description never says so explicitly as a usage rule.

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