Skip to main content
Glama

ChatStack - App Cost Estimator

Submit PRD and app estimate

submit_prd
Destructive

Submit the completed software PRD and app development estimate for email delivery and portal project creation. Call it only after user stories, requirements, tech specs, and the estimate exist. (flow_stage estimate). Run it for me stops at this tool. Offer submission and wait for the user. Do not submit it the way an empty send_action advances a milestone. Before calling, tell the user it emails the pack and creates a portal project. Propose first_name, last_name, email, country, and project_name already provided by the user, or a project name suggested by the tool. Show those values for confirmation and ask only for missing fields; if none are known, ask for all five. Set confirmed_by_user=true only after they confirm. Offer optional feedback and omit it if they skip. Never invent a contact field. If they decline, do not call this tool. Omit contact arguments the thread already collected. Pass the thread_id and interview_handle from the Session section. Success is only a ### PRD submitted notice plus project_id and version_id in the Session block. Relay post_submit_notice verbatim, including its line breaks and every URL, and do not add an email-delivery caveat. Do not show project_id or version_id to the user. A missing next_tool, a timeout, or an error is not success. If the result is unclear, call get_estimate_status. Do not call submit_prd again while that check is still unclear. Do not call submit_prd again after a receipt with both ids.

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": {
      "thread_id": "<thread_id>",
      "interview_handle": "<interview_handle>"
    },
    "name": "submit_prd"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoSuggested or confirmed email from user context.
countryNoSuggested or confirmed home country from user context.
feedbackNoOptional notes from the user (scope, questions, extra context). Ask, but omit if they skip. Never invent this.
last_nameNoSuggested or confirmed surname from user context.
thread_idYesInterview thread id from start_session.
first_nameNoSuggested or confirmed first name from user context.
project_nameNoSuggested or confirmed project name. Prefer values the user stated.
interview_handleYesOpaque interview handle from start_session. Pass it on every later tool.
confirmed_by_userNoSet true only after the user confirms the contact details (or corrects them).
interview_summaryNoOptional override; normally loaded from the thread

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations declare a destructive, non-read-only, open-world write, and the description adds substantial context beyond them: it emails the pack, creates a portal project, requires prior user confirmation, must not mutate contact fields, and defines success as a specific notice plus project_id/version_id. It also specifies relay rules for post_submit_notice and forbids re-submission, plus calls out that timeouts and errors are not success.

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?

Side effects and preconditions are front-loaded and nearly every sentence carries an actionable constraint, but the body is dense and mixes agent policy with tool semantics, and phrases like 'Run it for me stops at this tool' and the doubled 'do not call submit_prd again' clauses add friction. It is information-rich rather than padded, but tighter phrasing would help.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, multi-parameter submission tool with an output schema, this covers the gaps that matter: prerequisites, confirmation flow, what is emitted, what must not be shown, how to interpret ambiguous results, and when to stop retrying. Little an agent needs to call it correctly is absent.

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

Parameters5/5

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

Schema coverage is 100%, so a 3 would be the baseline, but the description goes further by specifying procedural meaning for parameters: propose the five contact/project fields from user context, display them for confirmation, ask only for missing ones, set confirmed_by_user=true only after confirmation, omit feedback if skipped, omit contact arguments already collected, and pass thread_id/interview_handle from the Session section.

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 (submit) plus the resources (software PRD and app development estimate) and the two concrete side effects: email delivery and portal project creation. This distinguishes it clearly from siblings like send_action, send_turn, and get_estimate_status.

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?

Explicit prerequisites ('only after user stories, requirements, tech specs, and the estimate exist'), an explicit stop condition ('Run it for me stops at this tool. Offer submission and wait'), a named alternative when the result is unclear (get_estimate_status), and explicit don't-call cases (user declines, already has a receipt). This is close to exhaustive when/when-not guidance.

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