Skip to main content
Glama

Synthex Forge — x402 Paid Agent Services

Evaluate Strategy Verdict

evaluate_strategy_verdict
Read-onlyIdempotent

Return ONE signed, dated strategy verdict. use it rather than evaluate_portfolio_verdict for strategy verdict, not portfolio verdict; an object with 62 fields including as_of, available. $2 USDC.

Input Schema

NameRequiredDescriptionDefault
as_ofNoThe date the answer is computed as of (YYYY-MM-DD). Defaults to today. Use it to reproduce a past answer exactly.
trialsNoThe trials this operation operates on. See the schema for its type and whether it is required.
returnsNoWhat the caller wants back.
claimed_sharpeNoThe claimed sharpe this operation operates on. See the schema for its type and whether it is required.
periods_per_yearNoThe periods per year this operation operates on. See the schema for its type and whether it is required.
benchmark_returnsNoThe return series to benchmark against.

Output Schema

NameRequiredDescriptionDefault
formNoThe `form` field of the response.
noteNoA note on how the answer was produced.
as_ofNoThe date the answer is computed as of.
routeNoThe `route` field of the response.
unitsNoThe `units` field of the response.
detailYesHuman-readable explanation of the verdict.
key_idNoThe `key_id` field of the response.
methodNoThe `method` field of the response.
reasonNoWhy the verdict was reached.
trialsNoThe `trials` field of the response.
p_valueNoThe `p_value` field of the response.
reasonsNoThe `reasons` field of the response.
verdictYesThe decision this tool returned.
versionNoThe `version` field of the response.
coverageNoHow much of the underlying corpus the answer is based on.
hardRuleNoThe `hardRule` field of the response.
readOnlyNoThe `readOnly` field of the response.
verdictsNoThe `verdicts` field of the response.
availableNoThe `available` field of the response.
signatureYesThe Ed25519 signature over the evidence core, base64-encoded.
signed_byNoThe key id that signed the answer.
stabilityNoThe `stability` field of the response.
statisticNoThe `statistic` field of the response.
beats_nullNoThe `beats_null` field of the response.
provenanceNoThe `provenance` field of the response.
public_keyNoThe `public_key` field of the response.
subperiodsNoThe `subperiods` field of the response.
calibrationNoThe `calibration` field of the response.
trials_usedNoThe `trials_used` field of the response.
capacityHintNoThe `capacityHint` field of the response.
observationsNoThe `observations` field of the response.
trialsSourceNoThe `trialsSource` field of the response.
coverage_gapsNoThe `coverage_gaps` field of the response.
evidence_coreYesThe canonical, signed core of the answer — the payload the signature covers.
output_sha256YesSHA-256 hex digest of the canonical evidence core.
subperiod_irsNoThe `subperiod_irs` field of the response.
trials_sourceNoThe `trials_source` field of the response.
claimed_sharpeNoThe `claimed_sharpe` field of the response.
deflated_sharpeNoThe `deflated_sharpe` field of the response.
multipleTestingNoThe `multipleTesting` field of the response.
observed_sharpeNoThe `observed_sharpe` field of the response.
population_sizeNoThe `population_size` field of the response.
subperiod_countNoThe `subperiod_count` field of the response.
canonicalizationNoThe canonicalisation rule the digest was computed under.
minimum_requiredNoThe `minimum_required` field of the response.
periods_per_yearNoThe `periods_per_year` field of the response.
threshold_sharpeNoThe `threshold_sharpe` field of the response.
vault_file_countNoThe `vault_file_count` field of the response.
capacity_hint_usdNoThe `capacity_hint_usd` field of the response.
vault_graded_countNoThe `vault_graded_count` field of the response.
worst_subperiod_irNoThe `worst_subperiod_ir` field of the response.
minimumObservationsNoThe `minimumObservations` field of the response.
signature_algorithmNoThe `signature_algorithm` field of the response.
claimed_sharpe_deltaNoThe `claimed_sharpe_delta` field of the response.
population_pass_rateNoThe `population_pass_rate` field of the response.
contaminated_excludedNoThe `contaminated_excluded` field of the response.
benchmark_observationsNoThe `benchmark_observations` field of the response.
contamination_excludedNoThe `contamination_excluded` field of the response.
null_expected_max_sharpeNoThe `null_expected_max_sharpe` field of the response.
population_median_sharpeNoThe `population_median_sharpe` field of the response.
observed_information_ratioNoThe `observed_information_ratio` field of the response.
multiple_testing_adjustmentNoThe `multiple_testing_adjustment` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed64 schema fields changed
    • addedOutput schema / properties / as_of
      Added value: +{
      +  "description": "The date the answer is computed as of.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / available
      Added value: +{
      +  "description": "The `available` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / beats_null
      Added value: +{
      +  "description": "The `beats_null` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / benchmark_observations
      Added value: +{
      +  "description": "The `benchmark_observations` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / calibration
      Added value: +{
      +  "description": "The `calibration` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / canonicalization
      Added value: +{
      +  "description": "The canonicalisation rule the digest was computed under.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / capacityHint
      Added value: +{
      +  "description": "The `capacityHint` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / capacity_hint_usd
      Added value: +{
      +  "description": "The `capacity_hint_usd` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / claimed_sharpe
      Added value: +{
      +  "description": "The `claimed_sharpe` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / claimed_sharpe_delta
      Added value: +{
      +  "description": "The `claimed_sharpe_delta` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / contaminated_excluded
      Added value: +{
      +  "description": "The `contaminated_excluded` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / contamination_excluded
      Added value: +{
      +  "description": "The `contamination_excluded` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / coverage
      Added value: +{
      +  "description": "How much of the underlying corpus the answer is based on.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / coverage_gaps
      Added value: +{
      +  "description": "The `coverage_gaps` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / deflated_sharpe
      Added value: +{
      +  "description": "The `deflated_sharpe` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / detail
      Added value: +{
      +  "description": "Human-readable explanation of the verdict.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / evidence_core
      Added value: +{
      +  "description": "The canonical, signed core of the answer — the payload the signature covers.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / form
      Added value: +{
      +  "description": "The `form` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / hardRule
      Added value: +{
      +  "description": "The `hardRule` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / key_id
      Added value: +{
      +  "description": "The `key_id` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / method
      Added value: +{
      +  "description": "The `method` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / minimumObservations
      Added value: +{
      +  "description": "The `minimumObservations` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / minimum_required
      Added value: +{
      +  "description": "The `minimum_required` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / multipleTesting
      Added value: +{
      +  "description": "The `multipleTesting` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / multiple_testing_adjustment
      Added value: +{
      +  "description": "The `multiple_testing_adjustment` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / note
      Added value: +{
      +  "description": "A note on how the answer was produced.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / null_expected_max_sharpe
      Added value: +{
      +  "description": "The `null_expected_max_sharpe` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / observations
      Added value: +{
      +  "description": "The `observations` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / observed_information_ratio
      Added value: +{
      +  "description": "The `observed_information_ratio` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / observed_sharpe
      Added value: +{
      +  "description": "The `observed_sharpe` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / output_sha256
      Added value: +{
      +  "description": "SHA-256 hex digest of the canonical evidence core.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / p_value
      Added value: +{
      +  "description": "The `p_value` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / periods_per_year
      Added value: +{
      +  "description": "The `periods_per_year` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / population_median_sharpe
      Added value: +{
      +  "description": "The `population_median_sharpe` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / population_pass_rate
      Added value: +{
      +  "description": "The `population_pass_rate` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / population_size
      Added value: +{
      +  "description": "The `population_size` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / provenance
      Added value: +{
      +  "description": "The `provenance` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / public_key
      Added value: +{
      +  "description": "The `public_key` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / readOnly
      Added value: +{
      +  "description": "The `readOnly` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / reason
      Added value: +{
      +  "description": "Why the verdict was reached.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / reasons
      Added value: +{
      +  "description": "The `reasons` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / route
      Added value: +{
      +  "description": "The `route` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / signature
      Added value: +{
      +  "description": "The Ed25519 signature over the evidence core, base64-encoded.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / signature_algorithm
      Added value: +{
      +  "description": "The `signature_algorithm` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / signed_by
      Added value: +{
      +  "description": "The key id that signed the answer.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / stability
      Added value: +{
      +  "description": "The `stability` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / statistic
      Added value: +{
      +  "description": "The `statistic` field of the response.",
      +  "type": "object"
      +}
    • removedOutput schema / properties / status
      Removed value: -{
      -  "type": "string"
      -}
    • addedOutput schema / properties / subperiod_count
      Added value: +{
      +  "description": "The `subperiod_count` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / subperiod_irs
      Added value: +{
      +  "description": "The `subperiod_irs` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / subperiods
      Added value: +{
      +  "description": "The `subperiods` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / threshold_sharpe
      Added value: +{
      +  "description": "The `threshold_sharpe` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / trials
      Added value: +{
      +  "description": "The `trials` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / trialsSource
      Added value: +{
      +  "description": "The `trialsSource` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / trials_source
      Added value: +{
      +  "description": "The `trials_source` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / trials_used
      Added value: +{
      +  "description": "The `trials_used` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / units
      Added value: +{
      +  "description": "The `units` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / vault_file_count
      Added value: +{
      +  "description": "The `vault_file_count` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / vault_graded_count
      Added value: +{
      +  "description": "The `vault_graded_count` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / verdict
      Added value: +{
      +  "description": "The decision this tool returned.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / verdicts
      Added value: +{
      +  "description": "The `verdicts` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / version
      Added value: +{
      +  "description": "The `version` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / worst_subperiod_ir
      Added value: +{
      +  "description": "The `worst_subperiod_ir` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / required
      Added value: +[
      +  "detail",
      +  "evidence_core",
      +  "output_sha256",
      +  "signature",
      +  "verdict"
      +]
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the description does not need to restate safety. It adds meaningful context beyond the annotations: the result is signed and dated, has 62 fields, and costs $2 USDC. It stops short of explaining payment mechanics or whether a failed call is still charged.

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 key purpose and sibling routing are front-loaded, and the cost notice earns its place. The phrasing is slightly compressed and the return-shape note ('62 fields including as_of, available') is less useful because an output schema already exists.

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?

With an output schema, full schema description coverage, and rich annotations, the description supplies the missing high-value context: signed/dated output, sibling differentiation, and the $2 USDC cost. It is mostly complete, though payment and failure-charge behavior remain unstated.

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 the schema already documents all six parameters. The description does not add parameter-level meaning beyond the schema; 'as_of' appears only as an example return field, not as an explanation of the input 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 states a specific verb and resource: 'Return ONE signed, dated strategy verdict.' It also explicitly distinguishes the tool from its closest sibling, `evaluate_portfolio_verdict`, so an agent can tell which verdict tool to choose without opening either schema.

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?

It gives an explicit routing rule: use this rather than `evaluate_portfolio_verdict` for a strategy verdict, not a portfolio verdict. That is precisely the kind of when-to-use/when-not-to-use guidance needed among many similarly named verdict tools.

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.