Skip to main content
Glama

bifrost-kfinance-mcp

preflight_validate

[$0.005 USDC] Deterministic pre-flight validator for JSON payloads, required keys, 5-field POSIX cron schedules, regex ReDoS safety, ISO-8601 timestamps, and target URL SSRF/syntax checks with a signed attestation hash.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "preflight_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
cronNo5-field cron schedule
regexNoRegular expression pattern
json_textNoRaw JSON string to validate
target_urlNoHTTP/HTTPS target URL
iso_timestampNoISO-8601 timestamp
required_keysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the price ($0.005 USDC), that results are deterministic, and that a signed attestation hash is produced, plus the security angle of the ReDoS and SSRF checks. However, it omits failure semantics (partial vs all-or-nothing results), what happens when zero parameters are passed (all are optional per schema), and any payment mechanics, which are material gaps for an unannotated tool.

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?

A single sentence with the price front-loaded in brackets and the check list ordered by parameter, so every clause maps to a usable capability. Nothing is filler, though the long comma-separated enumeration is dense and would scan faster as a short list or with one clause separating the attestation output from the check types.

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?

For a six-parameter, zero-required tool with no output schema and no annotations, the description covers what each check does and hints at the attestation return value. It leaves unclear whether parameters are independent and what an agent should expect back for a partial set, which matters more here than it would for an annotated tool. Adequate but not complete.

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 coverage is already 83%, so the baseline is 3, but the description earns above that by adding real meaning: the regex parameter is for checking ReDoS safety rather than matching, the target_url parameter is for SSRF/syntax checks rather than fetching, and cron is constrained to 5-field POSIX. These clarifications resolve genuine ambiguities the schema strings leave open. It does not explain how required_keys interacts with json_text, which prevents a 5.

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

Purpose4/5

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

The description names a specific verb (validate) and enumerates the exact resource classes it checks: JSON payloads, required keys, POSIX cron, regex ReDoS, ISO-8601 timestamps, and target URL SSRF/syntax. This maps almost one-to-one onto the six schema properties, so an agent knows precisely what the tool covers. It stops short of a 5 because it never says whether these checks run together or independently per call.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the phrase 'pre-flight validator', which suggests calling it before submitting or deploying a payload. There is no explicit when-to-use statement, no exclusion of cases, and no guidance on how many fields to supply per invocation. The sibling tools listed are unrelated, so no alternative routing is needed, but the absence of any explicit context keeps this at implied-only.

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.

Resources