Skip to main content
Glama
VrtxOmega

Mcp-Omega-Brain

by VrtxOmega
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Local

veritas_run_pipeline

Runs the complete 10-gate VERITAS pipeline to evaluate a BuildClaim, producing a verdict and gate-level results for end-to-end trust and auditability.

Instructions

Runs the full 10-gate VERITAS pipeline: INTAKE → TYPE → DEPENDENCY → EVIDENCE → MATH → COST → INCENTIVE → SECURITY → ADVERSARY → TRACE/SEAL. Use this for complete end-to-end evaluation of a BuildClaim; use individual gates for targeted checks. Returns JSON with fields: final_verdict (PASS | MODEL_BOUND | INCONCLUSIVE | VIOLATION), gate_results (array), reason_codes (array), seal_hash (hex string).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
claimYesA VERITAS BuildClaim object for deterministic gate evaluation. All fields are optional for partial evaluation — only fields relevant to the invoked gate are required.
fail_fastNoIf true (default), halts on first VIOLATION. Set false to collect all gate verdicts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removedv2.1.1
  3. Changed17 schema fields changedv1.0.2
    • changedInput schema / properties / claim / description
      Previous value: -"A VERITAS BuildClaim object containing all declared primitives, operators, regimes, boundaries, loss models, evidence items, cost vectors, and policy configuration needed for deterministic gate evaluation. All fields are optional for partial evaluation — only the fields relevant to the gate being invoked are required."New value: +"A VERITAS BuildClaim object for deterministic gate evaluation. All fields are optional for partial evaluation — only fields relevant to the invoked gate are required."
    • changedInput schema / properties / claim / properties / attack_suite / description
      Previous value: -"AttackSuite with suite_id and list of Attack transforms (InflateBound, RemoveEvidence, PerturbParam, PerturbEvidence) for adversary gate."New value: +"Attack transforms for adversary testing: InflateBound, RemoveEvidence, PerturbParam, PerturbEvidence."
    • changedInput schema / properties / claim / properties / boundaries / description
      Previous value: -"Named boundary constraints (e.g. 'CAPEX_USD <= 100000') that the claim must satisfy."New value: +"Boundary constraints, e.g. {name: 'cap', constraint: 'CAPEX_USD <= 100000'}."
    • changedInput schema / properties / claim / properties / commit / description
      Previous value: -"Git commit SHA for reproducibility and audit trail."New value: +"Git commit SHA for reproducibility."
    • changedInput schema / properties / claim / properties / cost / description
      Previous value: -"CostVector with optional fields: compute_flops, memory_bytes, wall_clock_s, capital_usd, coordination_agents."New value: +"CostVector: compute_flops, memory_bytes, wall_clock_s, capital_usd, coordination_agents."
    • changedInput schema / properties / claim / properties / cost_bounds / description
      Previous value: -"Upper bounds for each cost component. Utilization = max(cost_i / bound_i). Values must be > 0."New value: +"Upper bounds for each cost component. All values must be > 0."
    • changedInput schema / properties / claim / properties / dependencies / description
      Previous value: -"SBOM-style dependency manifest for supply-chain analysis: package names, versions, registries, and integrity hashes."New value: +"SBOM-style dependency manifest: package names, versions, registries, hashes."
    • changedInput schema / properties / claim / properties / evidence / description
      Previous value: -"Evidence items, each with id, variable, value (Numeric or Categorical), timestamp, method, provenance, and optional dependencies."New value: +"Evidence items with id, variable, value, timestamp, method, provenance."
    • changedInput schema / properties / claim / properties / loss_models / description
      Previous value: -"Named loss functions as ArithmeticExpr over primitives, with optional upper bounds."New value: +"Loss functions as ArithmeticExpr with optional upper bounds."
    • changedInput schema / properties / claim / properties / operators / description
      Previous value: -"Declared operators with name, arity, input primitive names, output primitive name, and totality flag."New value: +"Operators with name, arity, input/output primitive names, totality flag."
    • changedInput schema / properties / claim / properties / policy / description
      Previous value: -"PolicyConfig overrides: hash_alg, solver_backend, timeouts, thresholds. Defaults to VERITAS Omega v1.3.1 canonical values if omitted."New value: +"PolicyConfig overrides for hash_alg, solver_backend, timeouts, thresholds."
    • changedInput schema / properties / claim / properties / primitives / description
      Previous value: -"Declared typed variables with name, domain (Interval/EnumSet/FiniteSet), optional units, and description."New value: +"Typed variables with name, domain (Interval/EnumSet/FiniteSet), optional units."
    • changedInput schema / properties / claim / properties / project / description
      Previous value: -"Unique project identifier, e.g. 'omega-brain-mcp'."New value: +"Project identifier, e.g. 'omega-brain-mcp'."
    • changedInput schema / properties / claim / properties / regimes / description
      Previous value: -"Named operating regimes, each with a predicate ConstraintExpr over declared primitives."New value: +"Operating regimes with name and predicate ConstraintExpr."
    • changedInput schema / properties / claim / properties / security / description
      Previous value: -"Security posture declaration: SAST results, secret scan findings, injection surfaces, auth boundaries, and TLS/crypto configuration."New value: +"Security posture: SAST results, secret scan, injection surfaces, auth, TLS config."
    • changedInput schema / properties / claim / properties / version / description
      Previous value: -"Semantic version string of the build being evaluated, e.g. '2.1.0'."New value: +"Semantic version, e.g. '2.1.0'."
    • changedInput schema / properties / fail_fast / description
      Previous value: -"When true (default), halt the pipeline on the first VIOLATION verdict and skip remaining gates. Set to false to run all gates and collect every verdict."New value: +"If true (default), halts on first VIOLATION. Set false to collect all gate verdicts."
  4. Changed17 schema fields changedv1.0.1
    • changedInput schema / properties / claim / description
      Previous value: -"Full or partial VERITAS BuildClaim object"New value: +"A VERITAS BuildClaim object containing all declared primitives, operators, regimes, boundaries, loss models, evidence items, cost vectors, and policy configuration needed for deterministic gate evaluation. All fields are optional for partial evaluation — only the fields relevant to the gate being invoked are required."
    • addedInput schema / properties / claim / properties / attack_suite / description
      Added value: +"AttackSuite with suite_id and list of Attack transforms (InflateBound, RemoveEvidence, PerturbParam, PerturbEvidence) for adversary gate."
    • addedInput schema / properties / claim / properties / boundaries / description
      Added value: +"Named boundary constraints (e.g. 'CAPEX_USD <= 100000') that the claim must satisfy."
    • addedInput schema / properties / claim / properties / commit / description
      Added value: +"Git commit SHA for reproducibility and audit trail."
    • addedInput schema / properties / claim / properties / cost / description
      Added value: +"CostVector with optional fields: compute_flops, memory_bytes, wall_clock_s, capital_usd, coordination_agents."
    • addedInput schema / properties / claim / properties / cost_bounds / description
      Added value: +"Upper bounds for each cost component. Utilization = max(cost_i / bound_i). Values must be > 0."
    • addedInput schema / properties / claim / properties / dependencies / description
      Added value: +"SBOM-style dependency manifest for supply-chain analysis: package names, versions, registries, and integrity hashes."
    • addedInput schema / properties / claim / properties / evidence / description
      Added value: +"Evidence items, each with id, variable, value (Numeric or Categorical), timestamp, method, provenance, and optional dependencies."
    • addedInput schema / properties / claim / properties / loss_models / description
      Added value: +"Named loss functions as ArithmeticExpr over primitives, with optional upper bounds."
    • addedInput schema / properties / claim / properties / operators / description
      Added value: +"Declared operators with name, arity, input primitive names, output primitive name, and totality flag."
    • addedInput schema / properties / claim / properties / policy / description
      Added value: +"PolicyConfig overrides: hash_alg, solver_backend, timeouts, thresholds. Defaults to VERITAS Omega v1.3.1 canonical values if omitted."
    • addedInput schema / properties / claim / properties / primitives / description
      Added value: +"Declared typed variables with name, domain (Interval/EnumSet/FiniteSet), optional units, and description."
    • addedInput schema / properties / claim / properties / project / description
      Added value: +"Unique project identifier, e.g. 'omega-brain-mcp'."
    • addedInput schema / properties / claim / properties / regimes / description
      Added value: +"Named operating regimes, each with a predicate ConstraintExpr over declared primitives."
    • addedInput schema / properties / claim / properties / security / description
      Added value: +"Security posture declaration: SAST results, secret scan findings, injection surfaces, auth boundaries, and TLS/crypto configuration."
    • addedInput schema / properties / claim / properties / version / description
      Added value: +"Semantic version string of the build being evaluated, e.g. '2.1.0'."
    • changedInput schema / properties / fail_fast / description
      Previous value: -"Halt pipeline on first VIOLATION (spec default)"New value: +"When true (default), halt the pipeline on the first VIOLATION verdict and skip remaining gates. Set to false to run all gates and collect every verdict."
  5. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. Mentions it returns JSON with specific fields (final_verdict, gate_results, etc.), which is good. However, does not disclose potential side effects, authorization requirements, or runtime implications such as long execution time.

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

Conciseness5/5

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

Two concise sentences: first describes purpose and gates, second gives usage guidance and return format. No redundant or off-topic content. Front-loaded with essential 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?

Given the complexity (10 gates, large claim object), description covers purpose, usage distinction, and return structure. Lacks mention of prerequisites, order guarantees, or handling of errors. Output schema is not provided, so description compensates by listing return fields.

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 coverage is 100%, so baseline is 3. Description does not add detail beyond schema parameter descriptions; it focuses on return format. Does not clarify edge cases like partial claim objects or default behavior of fail_fast.

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?

Clearly states it runs the full 10-gate VERITAS pipeline end-to-end for evaluating a BuildClaim, listing all gate names. Differentiates from sibling gate tools by specifying 'use individual gates for targeted checks'.

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?

Explicitly tells when to use this tool ('complete end-to-end evaluation') and when to use alternatives ('use individual gates for targeted checks'). Provides clear decision guidance.

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