Skip to main content
Glama

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

check_proposal_or_edit_status

Zkontroluje živý stav asynchronní výroby návrhu webu v Továrně (~3 min) nebo stav bezplatných úprav dema na míru. Vrací state ('working' | 'completed' | 'input-required'), demoUrl jakmile je návrh online, shrnutí zapracovaných úprav a přímý objednávkový odkaz.

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

Input Schema

NameRequiredDescriptionDefault
icoNo8místné IČO firmy.
jobIdNoVolitelné ID výrobního jobu dema.
domainNoDoména firmy.
leadIdNoID poptávky / A2A úkolu vrácené při odeslání formuláře.
ticketIdNoVolitelné ID tiketu bezplatné úpravy dema.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 burden and does well: it discloses that the process is asynchronous (~3 min), lists the possible state values ('working' | 'completed' | 'input-required'), and explains that demoUrl appears once the proposal is online along with an edit summary and direct order link. It does not state authentication needs or whether repeated polling has any side effects, but for a status-check tool this is largely inferable from 'Zkontroluje živý stav'.

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 compact and front-loads the core purpose before the return details. The two sentences are dense but every element contributes useful information.

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?

For a moderately complex status tool with five optional parameters and no output schema, the description is fairly complete: it explains both checking modes, the approximate timing, and the return values. The main missing piece is explicit mapping of which parameter to pass for each mode, but the schema descriptions make this reasonably inferable.

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%, so all five parameters are documented in the schema itself. The description does not add guidance on which identifier to use for which mode (e.g., leadId for proposal status versus ticketId for demo edit status), so it adds little beyond the schema baseline.

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 specific verb and resource: it checks the live status of asynchronous website proposal production in the Factory or the status of free custom demo edits. The two modes are clearly described, though it does not explicitly name sibling tools to differentiate itself.

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?

Usage is implied: this is a status-polling tool used after submitting a proposal or requesting demo edits, with a ~3 minute production expectation. It does not explicitly state when not to use it or name alternatives such as inspecting a quote or submitting a new proposal.

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