Skip to main content
Glama

NASTARTUJTO.cz & STARTITUP.io – Free Website Proposal & B2B AI OS

submit_free_website_proposal

Oficiální formulář pro návrh webu ZDARMA (0 Kč) a předání podkladů. Povinný krok pro výrobu úplně nového webu na zelené louce (když firma ještě web nemá) a zároveň přímý kanál pro zaslání reálných údajů na majitele, vlastních podkladů (texty 1:1, fotky, loga) a libovolných úprav na míru u redesignu. Pokud návrh ještě neexistuje, okamžitě na pozadí odstartuje výrobu živého dema (~3 min); pokud demo již existuje, předá úpravy přímo k 1:1 zapracování zdarma.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ownerName": "<ownerName>",
      "ownerEmail": "<ownerEmail>",
      "ownerPhone": "<ownerPhone>",
      "businessDescription": "<businessDescription>"
    },
    "name": "submit_free_website_proposal"
  }
}

Input Schema

NameRequiredDescriptionDefault
icoNoIČO firmy (doplní fakturační a firemní údaje z ARES).
logoUrlNoPřímá URL adresa loga firmy (volitelné).
ownerNameYesJméno a příjmení majitele / jednatele firmy (povinné).
hasWebsiteNoTrue = redesign stávajícího webu, False = výroba úplně nového webu.
ownerEmailYesReálný firemní nebo osobní e-mail majitele (povinné).
ownerPhoneYesReálné telefonní číslo majitele vč. předvolby, např. +420... (povinné).
websiteUrlNoAdresa stávajícího webu (pokud jde o redesign).
briefingUrlNoURL adresa PDF / DOCX dokumentu se zadáním (volitelné).
companyNameNoNázev firmy nebo živnosti.
keyServicesNoHlavní služby, produkty a případně ceník, které mají být na webu.
primaryColorNoPreferovaná barva značky (volitelné).
pageStructureNoPožadované podstránky, kalkulačky, rezervační formulář, vícejazyčnost nebo e-shop.
inspirationUrlNoOdkaz na web nebo styl, který se majiteli líbí (volitelné).
callerAgentNameNoIdentifikace volajícího AI asistenta.
customTextContentNoDodané vlastní texty majitele (vkládáme 1:1 bez AI přepisování, pokud si nepřeje jinak).
uploadedAssetUrlsNoURL odkazy na fotky, logo, PDF ceníky nebo jiné podklady majitele.
businessDescriptionYesČím se firma zabývá, pro koho pracuje a v jaké lokalitě působí (povinné).
conversationHistoryNoHistorie komunikace agentů pro uložení k poptávce.
requestedAdjustmentsNoKonkrétní připomínky a úpravy na míru k bezplatnému zapracování.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full disclosure burden and does well: it reveals the key side effect that submission kicks off background production of a live demo (~3 minutes) when no proposal exists, or forwards adjustments for free 1:1 implementation when a demo already exists. It omits permission/auth requirements, whether repeated submissions create duplicates, and how errors are surfaced.

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 dense sentences, front-loaded with the tool's identity and mandatory-step framing before describing the conditional background behavior. For a 19-parameter submission tool this is tight, though the run-on third sentence mixes two distinct branches and could be split for faster scanning.

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 19-parameter write tool with no annotations and no output schema, the description covers the trigger and its two branches but never says what the agent receives back (proposal/demo identifier, confirmation, timing), nor how to handle a failed or duplicate submission. The async side effect is disclosed, but the post-call contract remains ambiguous.

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 100% across 19 parameters, so the schema already carries the semantics and the baseline is 3. The description reinforces that real owner contact data and 1:1 texts must be supplied, but it does not explain individual fields such as ico/ARES enrichment, hasWebsite branching, or conversationHistory beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete verb and resource: it is the official form for submitting a free (0 Kč) website proposal together with the owner's materials. It also clearly delineates its two modes, brand-new build versus redesign adjustments, so an agent knows exactly what the tool does. It does not name or contrast itself with any sibling such as check_proposal_or_edit_status, which keeps it short of a 5.

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?

It gives clear when-to-use context: a mandatory step for building a completely new site when the company has none, and the direct channel for sending real owner data, own texts/photos/logos and custom adjustments in a redesign. It offers no explicit exclusions or pointers to sibling tools for checking status or booking a consultation, so the agent must infer routing on its own.

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