Skip to main content
Glama

Generate the business-notes/ starter files

generate_starter_brief_files
Read-onlyIdempotent

Writes the eight business-notes/ files (00-start-here.md, business-facts.md, services-and-prices.md, faqs.md, policies.md, offers.md, decisions.md, voice.md) from what the owner has shared. Blanks become [Fill in: ...] lines so the bot sees the gap instead of guessing. Remove names, phone numbers and emails from samples first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "generate_starter_brief_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
faqsNoOne common question per line.
hoursNoDays and hours.
offersNoCurrent offers, each with an end date.
bot_nameNoWhat the bot is called.
industryNoThe kind of business.
policiesNoOne policy per line.
servicesNoOne service per line, with its price or range.
decisionsNoDecisions the owner has made, one per line.
owner_roleNoName and role for sign-offs.
voice_toneNoA few words on how the business sounds.
voice_neverNoLines for the Never list in voice.md.
what_you_doNoOne or two plain sentences.
service_areaNoTowns, region or "online".
business_nameNoThe business name.
voice_samplesNoReal messages the owner wrote, with personal details removed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior1/5

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

The description says the tool "Writes the eight business-notes/ files", which describes a filesystem mutation, while the annotations declare readOnlyHint=true and destructiveHint=false. That is a direct conflict about the tool's side effects. Helpful details such as the [Fill in: ...] placeholder behaviour do not resolve the question of whether existing files are overwritten.

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?

Three sentences, front-loaded with the resource and its contents, then the gap-filling rule, then the redaction precondition. Every sentence carries information; only the redaction instruction sits slightly awkwardly at the end rather than near the voice_samples parameter.

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?

For a 15-parameter generator with no output schema, the description covers the file manifest and blank handling but omits the return shape (file contents vs. paths vs. confirmation) and whether existing files are replaced. Given the annotation conflict around writing, that missing detail matters more than usual.

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?

All 15 parameters already carry schema descriptions at 100% coverage, so the schema does the heavy lifting. The description adds some meaning by tying inputs to specific output files (e.g. voice_samples to voice.md) and by stating that omitted inputs yield [Fill in: ...] lines, but it does not clarify which inputs map to which file or how partial input is handled.

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?

States a specific verb ("Writes") and resource (the eight business-notes/ files) and enumerates every file produced, so the agent knows exactly what output set to expect. This is clearly distinguishable from siblings such as audit_business_notes_freshness or analyze_voice_drift, which inspect rather than generate.

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 phrase "from what the owner has shared" implies the tool should be called after intake, and "Remove names, phone numbers and emails from samples first" gives a concrete precondition. However, no sibling is named, there is no explicit when-not guidance, and it never says whether this should follow start_guided_setup or be re-run against an existing notes directory.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources