Skip to main content
Glama
depsdev-mcp

depsdev-mcp

by Ankur1911

lookup_hash

Read-onlyIdempotent

Identify which package versions a file hash belongs to by accepting MD5, SHA1, SHA256, or SHA512 digests in hex or base64 and returning matching versions.

Instructions

Identify which package versions a file hash belongs to (for example the SHA-256 of a downloaded archive). Accepts hex or base64.

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": {
      "hash_type": "<hash_type>",
      "hash_value": "<hash_value>"
    },
    "name": "lookup_hash"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum matches to return.
hash_typeYesHash algorithm.
hash_valueYesDigest as a hex or base64 string.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety and repeatability profile is covered. The description adds essentially only the accepted encodings, which the schema also states, and says nothing about whether it searches a global index, what happens on zero matches, or result ordering.

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 tight sentences with zero padding, front-loading the outcome (which package versions) before the input hint. Nothing needs trimming and nothing is buried.

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 simple three-parameter read-only lookup with full schema coverage and clear annotations, the description is sufficient to call it correctly. A brief note on empty results or search scope would have closed the last gap, but it is not required to invoke the tool.

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% with all three parameters documented, so the baseline is 3. The description restates the hex-or-base64 acceptance but adds no meaning for hash_type's algorithm choice or for limit's role in capping matches.

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 plus resource: identify which package versions a file hash belongs to, with a concrete example (SHA-256 of a downloaded archive). An agent can tell this is a reverse-lookup over package content hashes, though it never names a sibling to contrast with.

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 the example — you have a digest of a downloaded file and want the originating package versions. There is no explicit when-not guidance and no routing to alternatives such as version_details or package_overview when the hash lookup fails or when the agent already knows the package name.

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