Skip to main content
Glama

subcontractor_acceptance_email

Write a professional email accepting a subcontracting role from a contractor or agency, confirming the role, start date, and standard conditions.

Instructions

Write the professional email confirming you are accepting a subcontracting role offered by another contractor or agency. Covers: confirming your acceptance, stating the agreed role and start date, and flagging any standard conditions (invoicing process, point of contact, NDA if applicable). Distinct from subcontractor_brief (you briefing someone YOU hired), bid_lost_follow_up (you lost a direct bid), and cold_pitch (you reaching out speculatively). Does not count against your monthly draft limit. Required: prime_name (name of the main contractor or agency), project_description (what the project is, e.g. 'the Acme Corp website redesign'), your_role (your specific role or deliverable, e.g. 'front-end development', 'UX design for the mobile flows'). Optional: start_date, rate_confirmation (e.g. '$120/hr as agreed', '$4,500 fixed fee'), point_of_contact (who you report to), nda_flag (if true, notes you are happy to sign an NDA), your_name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
prime_nameYesName of the main contractor, agency, or person who offered you the sub role
project_descriptionYesBrief description of the project (e.g. 'the Acme Corp website redesign', 'the Q3 brand campaign for TechStart')
your_roleYesYour specific role or deliverable on the project (e.g. 'front-end development', 'UX design for the mobile flows', 'copywriting for all campaign assets')
start_dateNoAgreed start date, if confirmed (e.g. 'Monday June 23', 'the week of July 7')
rate_confirmationNoRate or fee as agreed, to confirm in writing (e.g. '$120/hr', '$4,500 fixed fee for the full scope'). Omit if not yet confirmed.
point_of_contactNoName of the person you report to or coordinate with on the project, if known (e.g. 'Sarah', 'the PM on your side')
nda_flagNoIf true, adds a note that you are happy to sign an NDA or confidentiality agreement if required
your_nameNoYour name for the sign-off
Behavior4/5

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

With no annotations, the description carries full burden. It discloses that the tool generates an email draft (implied by 'Write' and 'does not count against your monthly draft limit'), but does not explicitly state whether it sends the email or is read-only. However, the nature is clear and no contradictions exist.

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 well-structured: a concise opening sentence, bullet-like coverage of email content, sibling differentiation, then parameter lists. Every sentence serves a purpose, and key info is front-loaded.

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?

Given the 8 parameters and no output schema or annotations, the description covers purpose, usage, parameter details, and a behavioral note (draft limit). It does not specify the return format, but that is acceptable without an output schema. Overall, it is nearly complete.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds value by grouping parameters into required/optional, providing real-world examples, and clarifying the purpose of each field (e.g., prime_name as 'name of the main contractor or agency'), going beyond schema descriptions.

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 writes a professional email for accepting a subcontracting role, specifying the verb 'Write' and the resource 'email'. It explicitly distinguishes from three siblings (subcontractor_brief, bid_lost_follow_up, cold_pitch), leaving no ambiguity.

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

Usage Guidelines5/5

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

Provides explicit context for when to use (accepting a subcontracting role) and directly names three sibling tools as distinct alternatives. Also mentions that it does not count against monthly draft limits, adding practical guidance.

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