Skip to main content
Glama
Offorte Proposal Software

Offorte Proposal Software

Official
by offorte

create_proposal

Create a new proposal by linking a contact, selected people, and proposal, text, and design templates, with optional custom fields and account user assignment.

Instructions

Create a new proposal

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": {
      "contact_id": "<contact_id>",
      "contact_people": "<contact_people>",
      "design_template_id": "<design_template_id>",
      "name": "<name>",
      "proposal_template_id": "<proposal_template_id>",
      "text_template_id": "<text_template_id>"
    },
    "name": "create_proposal"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
contact_idYes
custom_fieldsNo
contact_peopleYes
account_user_idNo
text_template_idYes
design_template_idYes
proposal_template_idYes

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

D1.7/5.0
Behavior1/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the write nature is known and not contradicted. However, the description adds nothing beyond that: it does not say whether the proposal is created as a draft or sent, what permissions or account_user_id scoping are required, what happens on failure, or what the call returns. For a multi-required-parameter mutation tool, this is a serious omission.

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?

The single short sentence contains no filler, so nothing is wasteful. But brevity here reflects under-specification rather than disciplined conciseness, and there is no structure carrying routing or prerequisite information.

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 create/mutation tool with 6 required parameters, no output schema, no annotation detail on side effects, and 0% parameter documentation. The definition gives an agent almost nothing it needs to invoke the tool correctly, which is far below what this complexity demands.

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?

The schema has 8 parameters (6 required) with 0% description coverage, and the description explains none of them. Cryptic fields such as contact_people (an array of numbers), design_template_id, proposal_template_id, text_template_id and account_user_id remain completely undefined, so the description does nothing to compensate for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create a new proposal' is essentially a de-camelCase of the tool name and title, with no added scope, resource context, or distinguishing detail. It gives no hint of how it differs from siblings such as copy_proposal or send_proposal, so it functions as a tautology rather than a real statement of purpose.

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 when-to-use guidance, no prerequisites (e.g. that the referenced templates and contact must already exist), and no mention of alternatives like copy_proposal. The agent must infer entirely on its own when this tool is the right choice.

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