Synthex Forge — x402 Paid Agent Services

Assess Dependency Risk

assess_dependency_risk

Read-onlyIdempotent

Risk analysis of a dependency set for a given ecosystem. use it rather than assess_tool_permission for dependency risk, not permission; an object with 42 fields including CRITICAL, HIGH. $0.2 USDC.

Input Schema

Name	Required	Description	Default
`ecosystem`	No	The ecosystem this operation operates on. See the schema for its type and whether it is required.	mixed
`dependencies`	No	The dependencies this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`LOW`	No	The `LOW` field of the response.
`cve`	No	The `cve` field of the response.
`low`	No	The `low` field of the response.
`HIGH`	No	The `HIGH` field of the response.
`cvss`	No	The `cvss` field of the response.
`desc`	No	The `desc` field of the response.
`high`	No	The `high` field of the response.
`info`	No	The `info` field of the response.
`note`	No	A note on how the answer was produced.
`type`	No	The `type` field of the response.
`clean`	No	The `clean` field of the response.
`stale`	No	The `stale` field of the response.
`title`	No	The `title` field of the response.
`MEDIUM`	No	The `MEDIUM` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`medium`	No	The `medium` field of the response.
`sha256`	No	The `sha256` field of the response.
`status`	No	The status of the operation.
`UNKNOWN`	No	The `UNKNOWN` field of the response.
`fixedIn`	No	The `fixedIn` field of the response.
`unknown`	No	The `unknown` field of the response.
`verdict`	Yes	The decision this tool returned.
`CRITICAL`	No	The `CRITICAL` field of the response.
`critical`	No	The `critical` field of the response.
`evidence`	No	The `evidence` field of the response.
`findings`	No	The `findings` field of the response.
`severity`	No	The `severity` field of the response.
`signedBy`	No	The `signedBy` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`ecosystem`	No	The `ecosystem` field of the response.
`riskLevel`	No	The `riskLevel` field of the response.
`sourceUrl`	No	The `sourceUrl` field of the response.
`dependency`	No	The `dependency` field of the response.
`deprecated`	No	The `deprecated` field of the response.
`ed25519Sig`	No	The `ed25519Sig` field of the response.
`vulnerable`	No	The `vulnerable` field of the response.
`dependencies`	No	The `dependencies` field of the response.
`publicKeyHex`	No	The `publicKeyHex` field of the response.
`canonicalSha256`	No	The `canonicalSha256` field of the response.
`reproducibility`	No	The `reproducibility` field of the response.
`requestedVersion`	No	The `requestedVersion` field of the response.
`dependenciesChecked`	No	The `dependenciesChecked` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed43 schema fields changedOct 31, 2026

addedOutput schema / properties / CRITICAL

Added value: +{
+  "description": "The `CRITICAL` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / HIGH

Added value: +{
+  "description": "The `HIGH` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / LOW

Added value: +{
+  "description": "The `LOW` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / MEDIUM

Added value: +{
+  "description": "The `MEDIUM` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / UNKNOWN

Added value: +{
+  "description": "The `UNKNOWN` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / algorithm

Added value: +{
+  "description": "The `algorithm` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / canonicalSha256

Added value: +{
+  "description": "The `canonicalSha256` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / clean

Added value: +{
+  "description": "The `clean` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / critical

Added value: +{
+  "description": "The `critical` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / cve

Added value: +{
+  "description": "The `cve` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / cvss

Added value: +{
+  "description": "The `cvss` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / dependencies

Added value: +{
+  "description": "The `dependencies` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / dependenciesChecked

Added value: +{
+  "description": "The `dependenciesChecked` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / dependency

Added value: +{
+  "description": "The `dependency` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / deprecated

Added value: +{
+  "description": "The `deprecated` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / desc

Added value: +{
+  "description": "The `desc` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / detail

Added value: +{
+  "description": "Human-readable explanation of the verdict.",
+  "type": "string"
+}

addedOutput schema / properties / ecosystem

Added value: +{
+  "description": "The `ecosystem` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / ed25519Sig

Added value: +{
+  "description": "The `ed25519Sig` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / evidence

Added value: +{
+  "description": "The `evidence` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / findings

Added value: +{
+  "description": "The `findings` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / fixedIn

Added value: +{
+  "description": "The `fixedIn` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / high

Added value: +{
+  "description": "The `high` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / info

Added value: +{
+  "description": "The `info` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / low

Added value: +{
+  "description": "The `low` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / medium

Added value: +{
+  "description": "The `medium` 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 / publicKeyHex

Added value: +{
+  "description": "The `publicKeyHex` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / reproducibility

Added value: +{
+  "description": "The `reproducibility` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / requestedVersion

Added value: +{
+  "description": "The `requestedVersion` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / riskLevel

Added value: +{
+  "description": "The `riskLevel` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / severity

Added value: +{
+  "description": "The `severity` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / sha256

Added value: +{
+  "description": "The `sha256` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / signedBy

Added value: +{
+  "description": "The `signedBy` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / sourceUrl

Added value: +{
+  "description": "The `sourceUrl` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / stale

Added value: +{
+  "description": "The `stale` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / status / description
```
Added value: +"The status of the operation."
```

addedOutput schema / properties / title

Added value: +{
+  "description": "The `title` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / type

Added value: +{
+  "description": "The `type` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / unknown

Added value: +{
+  "description": "The `unknown` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / verdict

Added value: +{
+  "description": "The decision this tool returned.",
+  "type": "string"
+}

addedOutput schema / properties / vulnerable

Added value: +{
+  "description": "The `vulnerable` field of the response.",
+  "type": "object"
+}

addedOutput schema / required

Added value: +[
+  "detail",
+  "verdict"
+]

AddedOct 31, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive), so the description adds genuinely new operational facts: a $0.2 USDC cost and the presence of severity levels like CRITICAL and HIGH. It does not describe rate limits or error behavior, and the output-shape remark is partly redundant with the existing output schema.

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

Conciseness3/5

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

Very short and front-loaded, which is good, but the second sentence is syntactically broken and interleaves the routing advice, the return-shape remark, and the price in a way that forces re-reading. Compression has cost clarity here.

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?

Annotations cover safety and an output schema exists, so those burdens are lifted. However, for a paid risk-analysis tool with two loosely documented parameters, the description leaves gaps on supported ecosystems, the dependency entry format, and what the caller actually receives beyond field count.

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 nominally 100%, so the baseline of 3 applies, but the schema text itself is generic boilerplate ('See the schema for its type'). The description adds nothing about what 'ecosystem' values are accepted or what a dependency entry looks like, so it neither helps nor harms.

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?

States a specific verb and resource: risk analysis of a dependency set within an ecosystem. It also names one sibling it is not (assess_tool_permission), though the crowded 'assess_*' family is only partially disambiguated.

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 routes the agent: use this rather than assess_tool_permission when the subject is dependency risk rather than permissions. The phrasing is garbled ('for dependency risk, not permission') and no preconditions or other alternatives are mentioned, keeping it below a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Synthex Forge — x402 Paid Agent Services tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.