ideaudit-tools
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| compute_barrierA | Compute barrier_score (0-24) + label (PRISTINE/OPEN/COMPETITIVE/CROWDED) from competitor counts + SERP noise fraction. |
| compute_budget_proofB | Compute budget_proof_score (0-10) + label (STRONG/CONFIRMED/WEAK/ABSENT) + purchase_intent_pct from pricing hits + review-site hits + intent mentions. |
| compute_build_complexityB | Compute build_complexity_penalty (0-10, higher = worse) + per-factor breakdown. Hard tags: ml/realtime/blockchain/hardware/compliance/custom-ai/regulated/on-device-ai/iot. |
| compute_collection_scoresA | Compute 12 deterministic collection scores (0-100) + badges + death reason for an enriched idea. Pure math. No external calls. |
| compute_crossed_matrixA | Crossed-product audit explorer. Same input as compute_dealbreakers_v2 — returns substrate verdict (no-observer baseline) + crossed verdict (when observer supplied) + a 5-row matrix of {solo, cofounded_technical, cofounded_business, domain_expert, serial} archetype verdicts. Never persists; meant for the dashboard "view as [archetype]" dropdown and for previewing a verdict before committing to it. |
| compute_dealbreakers_v2A | Methodology v2 dealbreakers — stage-aware weights + confidence-weighted lens scoring + risk-asymmetric verdict (GO requires score≥80 AND zero red flags AND avg confidence≥0.6). Optional |
| compute_funding_momentumC | Compute funding_momentum_score (0-10) + badge (HOT/WARM/COOL/COLD) from tier-weighted funding-article hit counts. |
| compute_hiring_demandC | Compute hiring_demand_score (0-10) from priority-weighted ATS site hit counts (use registries/hiring-sources for priorities). |
| compute_lrs_composite_v2A | LRS composite v2 — 6 components (SV, Pain, Barrier, Monet, X-Signal, Budget-Proof). Default Python weights 0.18/0.22/0.18/0.14/0.18/0.10 sum=1.0. Returns BOTH weighted score and equal-weight baseline (per OECD Handbook + Greco 2018 — equal-weight is defensible default when no outcome calibration exists). buildComplexityPenalty 0-10 subtracted from score. sectorProfile (ai_native/creator/crypto) opt-in reshuffles SV→0.16, X→0.20. Labels: THE_ROAR (≥80) / PROMISING (≥60) / EXPERIMENTAL (≥40) / WEAK_SIGNAL (<40). |
| compute_lrs_compositeB | Compose lrs_final_100 (0-100) + label (WEAK/EMERGING/GOOD/STRONG/ELITE) + leaderboard_eligible flag + sub-percent breakdown. Weights: sv 0.25, sp 0.30, barrier 0.25, monetization 0.20. |
| compute_monetizationB | Compute monetization_score (0-21) + label + has_pricing_anchors from pricing anchors + model tags + deal cycle hint. |
| compute_multi_source_tamA | Multi-source TAM consensus. Pass 2-3 sources of market-size text. Optional |
| compute_ppc_spend_signalA | Wave 5 N.4 — compute ppc_spend_score (0-10) + label (STRONG/CONFIRMED/WEAK/ABSENT) + market_saturation from PPC traffic projection (avgCpcUsd, totalMonthlySpendUsd, optional competitorBidders + competition). Feed numbers from dataforseo_ad_traffic. |
| compute_search_velocity_v2A | Search velocity (0-25) v2 — canonical 0.40volume + 0.30trend + 0.20intent + 0.10geo. CRITICAL: externalVolumeNorm MUST come from external sources (Amazon BSR / app store installs / job-board postings) — NOT the Trends timeline (would double-count, since Trends is itself normalized 0-100 within window). trendNorm is derived internally from trendsTimelineValues. Trends peak<50 zeroes the trend component (Yotpo SEO floor). Optional daysSinceLastSignal applies exponential freshness decay (search half-life 90d). |
| compute_search_velocityB | Compute search_velocity_score (0-25) from Trends timeline values + rising queries count + geo region count. |
| compute_social_painB | Compute social_pain_score (0-30) + total mentions + dominant perspective (business/consumer/trend/mixed). |
| compute_urgency_compositeA | Compose composite_urgency_score (0-10) + badge (LOW/MEDIUM/HIGH/VERY_HIGH/EXTREME) from 3 sub-scores: news, pain, hiring. |
| compute_x_signalB | Compute x_signal_score (0-20) + recency share + positivity rate from X/Twitter mention counts. |
| derive_kill_criteriaA | Derive a falsifiable, data-driven list of kill criteria from upstream signals — the outputs of validate_unit_economics and compute_dealbreakers_v2, plus an ICP drift count. Returns one row per rule with {rule, threshold, status, evidence?}, where status is tripped_now / monitor / cleared. Replaces prose kill criteria, which are tautologies that can never fire. |
| validate_unit_economicsA | Sanity-check a unit-economics row before publishing it in a business-model slide. Catches the math-drift class of failures (customers × ARPU ≠ revenue), enforces the LTV/CAC ≥ 1.5 floor, the cohort-positivity check, and CAC payback bounds. Returns {ok, errors[{rule, severity, detail}], derived{ratios}}. Skills MUST regenerate the row when ok=false (block-severity errors); warn-severity errors should be surfaced in the final report but do not gate publication. No LLM calls. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 20 tools
Several tools have unclear boundaries: compute_lrs_composite vs compute_lrs_composite_v2 and compute_search_velocity vs compute_search_velocity_v2 compute the same metric under different methodologies, while compute_crossed_matrix is explicitly same-input as compute_dealbreakers_v2. The detailed descriptions help, but the agent still needs versioning and nuance to avoid misselection.
Nearly every tool follows the same snake_case verb_noun pattern, either compute_<metric> or derive_/validate_<object>, and version suffixes like _v2 are used consistently. This makes the namespace highly predictable despite the large number of tools.
20 tools is at the heavy end for a single server, and the v1/v2 duplicate pairs inflate the count without adding clear separate domains. Most tools do have a specific computation, so the count is not unreasonable, but it feels borderline.
The set covers the full idea-audit arc: individual signals, composite scores, unit economics validation, and kill criteria. Minor gaps exist, such as no standalone news sub-score and legacy v1 tools creating ambiguous coverage, but agents can still assemble a complete workflow.