Skip to main content
Glama

nda_template

Create a plain-English non-disclosure agreement for freelance client work. Choose one-way or mutual confidentiality, set duration, and include exceptions and remedies clauses.

Instructions

Generate a simple, plain-English Non-Disclosure Agreement for freelance client work. Covers what's confidential, duration, exceptions, and a basic remedies clause. One-way (client's info stays confidential) or mutual. Not a substitute for legal advice — suitable for most standard freelance 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 project or engagement (e.g. 'website redesign', 'software development services')
duration_yearsNoHow long confidentiality obligations last in years (default: 2). Typical range: 1-5.
mutualNotrue = mutual NDA (both parties protect each other's info); false (default) = one-way (you protect the client's confidential information only)
governing_lawNoOptional: governing law jurisdiction (e.g. 'England and Wales', 'California, USA', 'New South Wales, Australia'). Leave blank to use a placeholder.
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool 'generates' an NDA and notes it does not affect draft limits, giving some insight into behavior. However, it does not explain what the tool returns (e.g., text content, downloadable file) or any side effects, which leaves moderate gaps for an agent.

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?

The description is concise at about 50 words, front-loading the main purpose and key features like coverage and options. It efficiently conveys essential information without redundancy, though a slightly more structured breakdown of clauses could improve clarity.

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

Completeness3/5

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

Given the tool has 6 parameters, no output schema, and moderate complexity, the description adequately covers the tool's purpose and key clauses. However, it lacks details about the output format or how the generated agreement is presented to the user, which is needed for complete understanding without an output schema.

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 covers all six parameters with descriptions, achieving 100% coverage. The description adds minimal extra meaning beyond the schema, only reiterating the one-way/mutual option. Since schema coverage is high, a baseline of 3 is appropriate, and the description does not significantly enhance parameter understanding.

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 Non-Disclosure Agreement for freelance client work, specifying it covers confidentiality, duration, exceptions, and remedies. It distinguishes between one-way and mutual NDAs, and notes it is not a substitute for legal advice. This effectively differentiates it from sibling tools like contract_template, which likely cover other contract types.

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

Usage Guidelines3/5

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

The description provides context by indicating the NDA is for 'freelance client work' and 'standard freelance engagements,' and it explicitly notes it does not count against a monthly draft limit. However, it does not mention when to avoid using this tool or suggest alternatives like contract_template for other legal documents, leaving some ambiguity.

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