Skip to main content
Glama

contract_template

Generate a plain-English Freelance Services Agreement covering services, payment, IP, revisions, termination, and liability. More comprehensive than an NDA and more legally framed than a SOW.

Instructions

Generate a plain-English Freelance Services Agreement — the full working contract covering services, payment, IP, revisions, termination, and liability. More comprehensive than an NDA (which covers only confidentiality) and more legally framed than a SOW (which covers deliverables). Suitable for most standard freelance and consulting engagements. Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
your_nameYesYour full name or company name (the service provider)
client_nameYesThe client's full name or company name
project_descriptionYesBrief description of the services being provided
total_priceYesTotal contract value (e.g. '$5,500', '$8,000 + expenses')
payment_termsNoHow and when payment is made (e.g. '50% on signing, 50% on delivery', 'monthly in advance', 'net-30 on invoice'). Default: 50% on signing, 50% on final delivery.
revision_roundsNoNumber of included revision rounds. Default: 2.
start_dateNoProject start date (optional, e.g. 'June 15, 2026')
governing_lawNoGoverning law jurisdiction (e.g. 'New South Wales, Australia', 'California, USA'). Optional.
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that the tool generates a full working contract in plain English and specifies it does not count against a draft limit. It does not detail any destructive effects or authentication needs, but the generation behavior is sufficiently clear.

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?

The description is three sentences, front-loaded with the primary action, followed by differentiation and suitability. Every sentence adds value without redundancy. It is highly efficient.

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?

Despite no output schema, the description adequately explains what the tool produces (a complete contract) and covers its main features. Given the parameter richness and sibling context, the description is complete enough for an agent to understand and use the tool correctly.

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?

The input schema has 100% description coverage for all 8 parameters, with clear descriptions for each. The tool's description does not add additional meaning beyond listing some contract areas, which are already implied by the parameter descriptions. Thus, baseline score is appropriate.

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 clearly states the tool generates a 'Freelance Services Agreement' and lists the areas it covers (services, payment, IP, revisions, termination, liability). It distinguishes itself from sibling tools by noting it is more comprehensive than an NDA and more legally framed than a SOW.

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 description provides context for when to use this tool (standard freelance/consulting engagements) and contrasts it with related tools (NDA, SOW). It also mentions it does not count against a monthly draft limit. However, it does not explicitly state when not to use it.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jabbawocky/proposalcraft'

If you have feedback or need assistance with the MCP directory API, please join our Discord server