Skip to main content
Glama

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

create_direct_checkout

Vygeneruje předvyplněný oficiální objednávkový odkaz https://startitup.io/objednavka (2letý provoz za 205 Kč/měs. bez DPH nebo 1letý provoz za 249 Kč/měs. bez DPH, s volbou okamžitého spuštění nebo dalšího bezplatného dolaďování na demu) a vrátí kompletní předávací kartu na osobní AI asistentku Kláru (klara@nastartujto.cz, +420 266 266 979).

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": "create_direct_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
icoNo8místné IČO klienta pro předvyplnění fakturačních údajů z ARES.
domainNoDoména klienta (volitelné).
ownerNameNo
ownerEmailNo
ownerPhoneNo
planMonthsNoDélka provozu: 24 měsíců (205 Kč/měs. – doporučeno) nebo 12 měsíců (249 Kč/měs.).
callerAgentNameNo
conversationHistoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose useful behavior: the pricing tiers, the choice between immediate launch and free tuning on a demo, and the exact contents of the returned handoff card including contact details. It does not say whether a record is persisted, whether anything is emailed to the client or assistant, or whether the generated link expires, which matters for a create_ operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Everything is packed into a single long sentence with nested parentheses, which makes it dense but front-loaded on the core action. The pricing parenthetical partly duplicates the planMonths schema description. It would read better split into a purpose sentence and a returns sentence.

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 an 8-parameter, zero-required creation tool with no annotations and no output schema, the description does cover the return artifact and pricing well. It leaves half the parameters unexplained and gives no side-effect, permission, or idempotency information, so an agent still lacks what it needs to call this confidently.

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 only 38%, so the description needs to compensate. It does add meaning for two parameters: the IČO drives ARES-based invoicing prefill, and the 205/249 Kč pricing maps the planMonths enum values to concrete outcomes. However ownerName, ownerEmail, ownerPhone, callerAgentName, conversationHistory and domain get no explanation anywhere, leaving a real gap.

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 names a concrete action (generating a prefilled official order link at startitup.io/objednavka) plus a concrete artifact returned (a handoff card for assistant Klára with email and phone). That is a specific verb+resource an agent can act on. It does not explicitly contrast itself with siblings like submit_free_website_proposal or inspect_company_and_quote, so it falls 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 Guidelines2/5

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

There is no statement of when to use this versus the other offer/proposal tools, and no prerequisites or exclusions. The agent must infer from the name and the pricing detail that this is the direct-purchase path. Usage is only implied, not guided.

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