Skip to main content
Glama

validate_idea

Validate a startup idea before writing code. Get a 10-dimension Venture Readiness Score, evidence brief, kill/pivot/test/build verdict, and founder-fit insights to avoid building dead-on-arrival products.

Instructions

Validate a startup idea before scaffolding code for it. Returns a scorecard (10-dimension Venture Readiness Score, 0–100), an evidence brief tagged by source (observed / inferred / AI / claim), a kill / pivot / test / build verdict, founder-fit calibration deltas if a skill graph is on file, and 1–3 archetype assignments with structural cautions for that cluster. Call this BEFORE writing project scaffolding when the user is greenfield-building from a raw idea.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rawIdeaYesThe idea to validate. Free-form text; mess is fine — Trigvale normalizes it. Be specific about who has the pain, who pays, and why now.
saveNoWhen true, persist the brief to the user's vault so they can revisit it at trigvale.com/ideas/{id}. Default true. Set false for ephemeral checks.

Implementation Reference

  • Zod schema for validate_idea arguments: rawIdea (string, 5-4000 chars) and save (optional boolean, default true).
    const ValidateIdeaArgsSchema = z.object({
      rawIdea: z
        .string()
        .min(5)
        .max(4000)
        .describe(
          "The idea to validate. Free-form text; mess is fine — Trigvale normalizes it. Be specific about who has the pain, who pays, and why now.",
        ),
      save: z
        .boolean()
        .optional()
        .default(true)
        .describe(
          "When true, persist the brief to the user's vault so they can revisit it at trigvale.com/ideas/{id}. Default true. Set false for ephemeral checks.",
        ),
    });
  • src/index.ts:65-92 (registration)
    Registers the validate_idea tool in ListToolsRequestSchema handler with description and inputSchema.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        {
          name: "validate_idea",
          description:
            "Validate a startup idea before scaffolding code for it. Returns a scorecard (10-dimension Venture Readiness Score, 0–100), an evidence brief tagged by source (observed / inferred / AI / claim), a kill / pivot / test / build verdict, founder-fit calibration deltas if a skill graph is on file, and 1–3 archetype assignments with structural cautions for that cluster. Call this BEFORE writing project scaffolding when the user is greenfield-building from a raw idea.",
          inputSchema: {
            type: "object",
            properties: {
              rawIdea: {
                type: "string",
                minLength: 5,
                maxLength: 4000,
                description:
                  "The idea to validate. Free-form text; mess is fine — Trigvale normalizes it. Be specific about who has the pain, who pays, and why now.",
              },
              save: {
                type: "boolean",
                default: true,
                description:
                  "When true, persist the brief to the user's vault so they can revisit it at trigvale.com/ideas/{id}. Default true. Set false for ephemeral checks.",
              },
            },
            required: ["rawIdea"],
          },
        },
      ],
    }));
  • Main handler for CallToolRequestSchema: parses args, calls POST /agent/v1/evaluate, and returns both a human-readable summary and full JSON result.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      if (request.params.name !== "validate_idea") {
        throw new Error(`Unknown tool: ${request.params.name}`);
      }
    
      const args = ValidateIdeaArgsSchema.parse(request.params.arguments ?? {});
    
      const res = await fetch(`${apiBase}/agent/v1/evaluate`, {
        method: "POST",
        headers: {
          "content-type": "application/json",
          authorization: `Bearer ${agentToken}`,
        },
        body: JSON.stringify({ rawIdea: args.rawIdea, save: args.save }),
      });
    
      if (!res.ok) {
        const text = await res.text();
        throw new Error(`Trigvale API ${res.status}: ${text || res.statusText}`);
      }
    
      const body = (await res.json()) as AgentEvaluateResponse;
    
      // Return both the structured object (for agent reasoning) and a
      // human-readable summary block (for chat clients that just render text).
      return {
        content: [
          {
            type: "text",
            text: summarize(body),
          },
          {
            type: "text",
            text: "```json\n" + JSON.stringify(body, null, 2) + "\n```",
          },
        ],
      };
    });
  • TypeScript interface AgentEvaluateResponse defining the shape of the API response.
    interface AgentEvaluateResponse {
      ideaObject: { title: string };
      scorecard: { vrs: number; confidence: string };
      verdict: { verdict: string; reasons: string[] };
      founderAdjustments?: { dimension: string; delta: number; reason: string }[];
      archetypeAssignments?: { archetype: string; confidence: string; rationale: string }[];
      saved?: { ideaId: string } | null;
    }
  • Helper function summarize() that formats the API response into a human-readable markdown summary.
    function summarize(body: AgentEvaluateResponse): string {
      const lines: string[] = [];
      lines.push(`# ${body.ideaObject.title}`);
      lines.push("");
      lines.push(
        `**Verdict: ${body.verdict.verdict.toUpperCase()}** · VRS ${body.scorecard.vrs}/100 · ${body.scorecard.confidence} confidence`,
      );
      lines.push("");
      if (body.verdict.reasons?.length) {
        for (const r of body.verdict.reasons) lines.push(`- ${r}`);
        lines.push("");
      }
      if (body.archetypeAssignments?.length) {
        const top = body.archetypeAssignments[0]!;
        lines.push(`Archetype: **${top.archetype}** (${top.confidence}) — ${top.rationale}`);
        lines.push("");
      }
      if (body.founderAdjustments?.length) {
        lines.push("Founder-fit calibration applied:");
        for (const a of body.founderAdjustments) {
          lines.push(`- ${a.dimension}: ${a.delta > 0 ? "+" : ""}${a.delta} (${a.reason})`);
        }
        lines.push("");
      }
      if (body.saved?.ideaId) {
        lines.push(`Saved to vault: https://trigvale.com/ideas/${body.saved.ideaId}`);
      }
      return lines.join("\n");
    }
Behavior4/5

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

With no annotations provided, the description fully carries the burden of behavioral disclosure. It lists exact return values (scorecard, evidence brief, verdict, deltas, archetypes) and mentions conditional behavior ('if a skill graph is on file'). It also notes the persistence behavior tied to the `save` parameter.

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 but includes necessary detail. It front-loads the core action ('Validate a startup idea before scaffolding code for it.'), then lists outputs efficiently. A very slight verbosity in listing all outputs prevents a perfect 5, but it remains well-structured.

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?

Given the tool's moderate complexity (2 parameters, no output schema, no annotations), the description provides sufficient context: it explains the full return structure, conditional behavior, and persistence options. No obvious gaps remain for an LLM to select and invoke the tool correctly.

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

Parameters4/5

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

Schema description coverage is 100%, and the description adds valuable usage hints beyond the schema: for `rawIdea` it advises specificity and normalizes messiness; for `save` it explains default behavior and ephemeral usage. This enriches the agent's understanding of each parameter.

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?

The description opens with a clear action-verb+resource: 'Validate a startup idea before scaffolding code for it.' It unambiguously states the tool's function and context, distinguishing it from potential siblings by specifying the prerequisite step.

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?

The description explicitly tells when to use the tool: 'Call this BEFORE writing project scaffolding when the user is greenfield-building from a raw idea.' While it doesn't mention when not to use it or alternatives, the guidance is clear and actionable given no sibling tools exist.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sydacos-development/trigvale-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server