Skip to main content
Glama

Check Zcash code

zcash_check

Lint Zcash code, config, or shell commands for outdated patterns and privacy leaks before deployment, catching dead servers, Orchard pool use, and exposed spending keys.

Instructions

Lints code, config or shell commands for outdated Zcash patterns (dead servers, the Orchard pool, WebZjs, v4 transactions, 75-second blocks, fixed fees) and privacy leaks (spending keys on servers, transparent funding, personal data in memos, logged keys).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "code": "<code>"
    },
    "name": "zcash_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesSource code, config or shell commands to check.
filenameNoFile name, used only to label the findings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and it does not say whether this is read-only, whether it uploads code anywhere, whether findings are blocking, or how results are reported. It does list the detection categories, which is genuine behavioral content, but operational traits such as safety, side effects and response shape are absent.

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?

One front-loaded sentence with the verb first and the two finding categories grouped in parentheses; every item listed is a concrete detectable pattern. The parenthetical is long but dense with useful signal rather than filler.

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

Completeness2/5

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

For a linter with no annotations and no output schema, the definition should indicate what findings look like, whether they are advisory or blocking, and whether anything is transmitted remotely. None of that is addressed, leaving an agent unsure how to interpret or act on results.

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 description coverage is 100%, so both parameters are documented, and the description adds the important detail that config and shell commands are also in scope, not just source code. It does not explain the 200000-character limit or how filename influences output beyond labeling, but the schema already covers the basics.

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?

States a specific verb (lints) plus the resource (code, config or shell commands) and enumerates the exact classes of issues detected: outdated Zcash patterns and privacy leaks. That is specific enough to distinguish it from sibling tools like zcash_now, zcash_recipe and zcash_tx_status.

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 implied by 'Lints code, config or shell commands' — an agent can infer it applies before shipping or reviewing Zcash code — but there is no explicit when-to-use versus alternatives and no stated exclusions relative to the siblings. The scope is clear, the routing guidance is not.

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

Deploy Server

Other Tools