Skip to main content
Glama
theluckystrike

mcp-office-suite

by theluckystrike
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Hybrid

Create a proposal

proposal_create

Generate a client-ready Word proposal from project summary, scope, deliverables, timeline, price, and terms. Returns the reference, total, and file path for direct use.

Instructions

Call this tool to produce a client-ready .docx proposal from summary, scope, deliverables, timeline, price and terms. Returns the reference, the total and the file path. Free tier: 3 proposals or contracts per month.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
priceYes
scopeNoWhat is in scope, one bullet each. Omitted from the document if not given or empty
clientYesClient name, printed as 'Prepared for'. The letterhead comes from your business_set profile
summaryNoOne or two paragraphs on the problem and the approach. Omitted from the document if not given
out_pathNoWhere to write the .docx. Defaults to the data directory
timelineNoPhases and their durations, rendered as a table. Omitted from the document if not given or empty
overwriteNoReplace out_path if a file is already there. Default false: an existing file is never overwritten
valid_untilNoYYYY-MM-DD, the date the quote expires
deliverablesNoWhat the client receives, one bullet each. Omitted from the document if not given or empty
project_titleYesProject title

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.20.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden. It discloses output semantics (reference, total, file path) and a free-tier quota, both of which are not inferable from the schema. It does not mention overwrite behavior, but the schema's overwrite parameter covers that specific detail.

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?

Two sentences, front-loaded with the action and output, with no wasted words. The quota note is a single useful clause that an agent needs for planning.

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

Completeness4/5

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

The tool has 10 parameters, nested objects, and no output schema, so the description must clarify return values; it does so by stating reference, total, and file path. It also adds quota context. Some details such as letterhead source and overwrite policy are left to the schema, but the schema documents them well.

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 description coverage is 90%, so the schema already documents the parameters in detail. The description lists summary, scope, deliverables, timeline, price, and terms as input categories, but adds no per-parameter meaning beyond what the schema provides.

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?

The description states a specific verb ('produce') and resource ('client-ready .docx proposal') and lists the major input categories. It is clearly distinguished from proposal_update by its creation focus and from contract tools by the proposal-specific output.

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?

The opening instruction 'Call this tool to produce a client-ready .docx proposal' gives a direct, clear use case. It does not explicitly name alternatives or when-not-to-use cases, but the purpose is specific enough that an agent can route to it for proposal generation.

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

Install Server

Other Tools