Skip to main content
Glama

Release: check a downloaded file

release_check
Read-only

Check that a file you downloaded is part of a release its maker sealed with Privi, and see which company, product and version it belongs to. No organization key needed.

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": {
      "file_sha256": "<file_sha256>"
    },
    "name": "release_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_sha256YesSHA-256 of the file you downloaded

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a genuine piece of behavioral context the annotations do not: no organization key is required. It does not disclose what happens when the file is not part of any sealed release (error vs. negative result), which is the main behavioral unknown for a check 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?

Two sentences, front-loaded with the core action and followed by the useful authentication exemption. Every clause carries information and nothing is padded.

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?

For a one-parameter, read-only check with no output schema, the description covers the action, the input context, the returned metadata, and the auth exemption. The only meaningful gap is the outcome semantics of a failed or negative check.

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 single file_sha256 parameter is already fully documented in the schema. The description only implies that the input is a downloaded file and never mentions that a hash is what must be supplied, so it adds little beyond the structured field.

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 pairs a specific verb ('check') with a specific resource ('a file you downloaded ... part of a release') and even states the information returned (company, product, version). It implicitly separates itself from the sealing counterpart by framing the input as something 'its maker sealed with Privi', though it never names release_seal explicitly.

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?

'Check that a file you downloaded' establishes the triggering context clearly — this is a post-download verification step. 'No organization key needed' removes a prerequisite an agent might otherwise assume. It stops short of stating when not to use it or naming an alternative tool for other verification flows.

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