Skip to main content
Glama

Synthex Forge — x402 Paid Agent Services

Create Fund Tearsheet

create_fund_tearsheet
Destructive

Compute the tearsheet. use it rather than create_sla_breach_evidence for fund tearsheet, not sla breach evidence; an object with 56 fields including alpha, benchmark. $5 USDC.

Input Schema

NameRequiredDescriptionDefault
returnsNoWhat the caller wants back.
risk_freeNoThe risk free 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
llmNoThe `llm` field of the response.
volNoThe `vol` field of the response.
betaNoThe `beta` field of the response.
cagrNoThe `cagr` field of the response.
kindNoThe `kind` field of the response.
noteNoA note on how the answer was produced.
skewNoThe `skew` field of the response.
alphaNoThe `alpha` field of the response.
clockNoThe `clock` field of the response.
calmarNoThe `calmar` field of the response.
key_idNoThe `key_id` field of the response.
sharpeNoThe `sharpe` field of the response.
hitRateNoThe `hitRate` field of the response.
periodsNoThe `periods` field of the response.
profileNoThe `profile` field of the response.
sortinoNoThe `sortino` field of the response.
verdictYesThe decision this tool returned.
formulasNoThe `formulas` field of the response.
hit_rateNoThe `hit_rate` field of the response.
kurtosisNoThe `kurtosis` field of the response.
strategyNoThe `strategy` field of the response.
verdictsNoThe `verdicts` field of the response.
benchmarkNoThe `benchmark` field of the response.
risk_freeNoThe `risk_free` field of the response.
signatureYesThe Ed25519 signature over the evidence core, base64-encoded.
signed_byNoThe key id that signed the answer.
bestPeriodNoThe `bestPeriod` field of the response.
input_ruleNoThe `input_rule` field of the response.
public_keyNoThe `public_key` field of the response.
best_periodNoThe `best_period` field of the response.
correlationNoThe `correlation` field of the response.
maxDrawdownNoThe `maxDrawdown` field of the response.
methodologyNoThe `methodology` field of the response.
min_periodsNoThe `min_periods` field of the response.
worstPeriodNoThe `worstPeriod` field of the response.
coverageGapsNoThe `coverageGaps` field of the response.
max_drawdownNoThe `max_drawdown` field of the response.
worst_periodNoThe `worst_period` 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.
formulaVersionNoThe `formulaVersion` field of the response.
missing_fieldsNoThe `missing_fields` field of the response.
profileVersionNoVersion of the answer profile.
dropped_periodsNoThe `dropped_periods` field of the response.
overlap_periodsNoThe `overlap_periods` field of the response.
profile_versionNoVersion of the answer profile.
canonicalizationNoThe canonicalisation rule the digest was computed under.
periods_per_yearNoThe `periods_per_year` field of the response.
periods_requiredNoThe `periods_required` field of the response.
sample_sd_periodNoThe `sample_sd_period` field of the response.
mean_period_returnNoThe `mean_period_return` field of the response.
methodologyVersionNoThe `methodologyVersion` field of the response.
benchmark_alignmentNoThe `benchmark_alignment` field of the response.
methodology_versionNoVersion of the method that produced the answer.
signature_algorithmNoThe `signature_algorithm` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed58 schema fields changed
    • addedOutput schema / properties / alpha
      Added value: +{
      +  "description": "The `alpha` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / benchmark
      Added value: +{
      +  "description": "The `benchmark` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / benchmark_alignment
      Added value: +{
      +  "description": "The `benchmark_alignment` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / bestPeriod
      Added value: +{
      +  "description": "The `bestPeriod` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / best_period
      Added value: +{
      +  "description": "The `best_period` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / beta
      Added value: +{
      +  "description": "The `beta` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / cagr
      Added value: +{
      +  "description": "The `cagr` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / calmar
      Added value: +{
      +  "description": "The `calmar` 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 / clock
      Added value: +{
      +  "description": "The `clock` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / correlation
      Added value: +{
      +  "description": "The `correlation` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / coverageGaps
      Added value: +{
      +  "description": "The `coverageGaps` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / coverage_gaps
      Added value: +{
      +  "description": "The `coverage_gaps` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / dropped_periods
      Added value: +{
      +  "description": "The `dropped_periods` field of the response.",
      +  "type": "object"
      +}
    • 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 / formulaVersion
      Added value: +{
      +  "description": "The `formulaVersion` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / formulas
      Added value: +{
      +  "description": "The `formulas` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / hitRate
      Added value: +{
      +  "description": "The `hitRate` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / hit_rate
      Added value: +{
      +  "description": "The `hit_rate` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / input_rule
      Added value: +{
      +  "description": "The `input_rule` 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 / kind
      Added value: +{
      +  "description": "The `kind` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / kurtosis
      Added value: +{
      +  "description": "The `kurtosis` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / llm
      Added value: +{
      +  "description": "The `llm` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / maxDrawdown
      Added value: +{
      +  "description": "The `maxDrawdown` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / max_drawdown
      Added value: +{
      +  "description": "The `max_drawdown` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / mean_period_return
      Added value: +{
      +  "description": "The `mean_period_return` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / methodology
      Added value: +{
      +  "description": "The `methodology` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / methodologyVersion
      Added value: +{
      +  "description": "The `methodologyVersion` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / methodology_version
      Added value: +{
      +  "description": "Version of the method that produced the answer.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / min_periods
      Added value: +{
      +  "description": "The `min_periods` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / missing_fields
      Added value: +{
      +  "description": "The `missing_fields` 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 / output_sha256
      Added value: +{
      +  "description": "SHA-256 hex digest of the canonical evidence core.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / overlap_periods
      Added value: +{
      +  "description": "The `overlap_periods` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / periods
      Added value: +{
      +  "description": "The `periods` 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 / periods_required
      Added value: +{
      +  "description": "The `periods_required` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / profile
      Added value: +{
      +  "description": "The `profile` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / profileVersion
      Added value: +{
      +  "description": "Version of the answer profile.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / profile_version
      Added value: +{
      +  "description": "Version of the answer profile.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / public_key
      Added value: +{
      +  "description": "The `public_key` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / risk_free
      Added value: +{
      +  "description": "The `risk_free` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / sample_sd_period
      Added value: +{
      +  "description": "The `sample_sd_period` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / sharpe
      Added value: +{
      +  "description": "The `sharpe` 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 / skew
      Added value: +{
      +  "description": "The `skew` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / sortino
      Added value: +{
      +  "description": "The `sortino` field of the response.",
      +  "type": "object"
      +}
    • removedOutput schema / properties / status
      Removed value: -{
      -  "type": "string"
      -}
    • addedOutput schema / properties / strategy
      Added value: +{
      +  "description": "The `strategy` 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 / vol
      Added value: +{
      +  "description": "The `vol` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / worstPeriod
      Added value: +{
      +  "description": "The `worstPeriod` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / worst_period
      Added value: +{
      +  "description": "The `worst_period` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / required
      Added value: +[
      +  "evidence_core",
      +  "output_sha256",
      +  "signature",
      +  "verdict"
      +]
  2. Added

TDQS

B3.4/5.0
Behavior3/5

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

Adds genuinely useful context beyond annotations by disclosing the cost ('$5 USDC') and the shape of the result (56 fields including alpha, benchmark). However, it does not explain why the tool is flagged destructive/non-idempotent, nor whether the charge occurs per call or on failure — relevant for a paid mutation-flagged tool.

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?

Roughly 30 words with the core purpose, the sibling routing, the output shape and the price all present; the semicolon-separated clauses make it dense and front-loaded rather than padded.

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

Completeness3/5

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

Return values are covered by the output schema, so explaining them is unnecessary, and the cost plus sibling disambiguation are covered. What is missing is any hint about what the parameters mean in practice or what the destructive/non-idempotent flags imply for a caller.

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 four parameters (returns, risk_free, periods_per_year, benchmark_returns) are already documented in the schema. The description adds nothing about parameter meaning or defaults, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

'Compute the tearsheet' largely restates the tool name, but the follow-on clause clarifies it is a fund tearsheet (not SLA breach evidence) and that it returns a 56-field object with alpha and benchmark. That gives an agent enough to identify the capability, though the verb+resource is not stated more specifically than the name.

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?

Explicitly names an alternative, `create_sla_breach_evidence`, and states the condition ('for fund tearsheet, not sla breach evidence'). That is a real routing rule between siblings, even if the phrasing is awkward and no other alternatives or prerequisites are mentioned.

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.