Skip to main content
Glama

Known-bad hash lookup (free)

known_bad_lookup
Read-onlyIdempotent

Check a SHA-256 against Lazaretto's known-bad indicator set (refreshed daily from abuse.ch). Free and anonymous. A miss only means this exact hash is not in the indicator set; it is not a clean verdict on the artifact.

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": {
      "sha256": "<sha256>"
    },
    "name": "known_bad_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
sha256Yes64 hex chars, optionally sha256: prefixed

Output Schema

NameRequiredDescriptionDefault
known_badYesmatched is true on a hit, false on a miss. A miss is not a verdict on the artifact.
disclaimerNo
target_hashYesThe hash that was looked up, sha256: prefixed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "disclaimer": {
      +      "type": "string"
      +    },
      +    "known_bad": {
      +      "description": "matched is true on a hit, false on a miss. A miss is not a verdict on the artifact.",
      +      "properties": {
      +        "match_type": {
      +          "type": "string"
      +        },
      +        "matched": {
      +          "description": "null means the indicator set could not be consulted (fail closed), never treat null as clean.",
      +          "type": [
      +            "boolean",
      +            "null"
      +          ]
      +        },
      +        "note": {
      +          "type": "string"
      +        },
      +        "sources": {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        }
      +      },
      +      "required": [
      +        "matched"
      +      ],
      +      "type": "object"
      +    },
      +    "target_hash": {
      +      "description": "The hash that was looked up, sha256: prefixed.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "target_hash",
      +    "known_bad"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Adds substantial context beyond the rich annotations: data provenance (abuse.ch), refresh cadence (daily), authentication requirements (free and anonymous), and crucially the semantics of a miss. The warning that a miss is not a clean verdict directly prevents a dangerous misinterpretation of a negative result.

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?

Three short sentences, each earning its place: purpose first, operating context second, result-interpretation caveat third. Nothing is repeated or wasted, and the most important caveat is clearly stated.

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

Completeness5/5

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

Given a single fully documented parameter, rich annotations, and an output schema, the description supplies everything else an agent needs: what is checked, where the data comes from, freshness, access model, and the key limitation of negative results. No material gap remains.

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%, and the only parameter is fully documented as '64 hex chars, optionally sha256: prefixed'. The description mentions SHA-256 but adds no format, prefix-handling, or validation details beyond what the schema already provides, so baseline 3 is appropriate.

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: checking a SHA-256 against a named known-bad indicator set. The scope is tight enough to distinguish it from artifact-scanning siblings implicitly, but it never names an alternative, so differentiation is left to inference.

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?

'Free and anonymous' implies this is a lightweight check, and the miss caveat tells the agent not to over-read a negative result. However, there is no explicit guidance on when to use this versus scan_artifact, scan_lockfile_deep, or other siblings that provide deeper verdicts.

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.