Skip to main content
Glama
starshield-forensics

starshield-forensics

by Ziqi

Run StarShield Clean-Room Synthetic Demo

starshield_demo
Read-onlyIdempotent

Runs five deterministic offline triage engines on synthetic vectors to validate LevelDB WAL CRC32C carving, PNG/JPEG container inspection, financial checksums, and UTC timestamp corroboration.

Instructions

Execute StarShield's 5 deterministic offline triage engines on embedded 100% synthetic specification vectors (LevelDB 32KiB CRC32C WAL carving, PNG/JPEG ICC & 8BIM container inspection, Luhn/IBAN Mod-97/SWIFT validation, and UTC timestamp corroboration).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "starshield_demo"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false). The description adds genuine context beyond them: the run is deterministic, offline, and operates on 100% synthetic embedded vectors, so no external data or network is touched. However, it says nothing about what the run returns or how results are reported, which matters for a no-output-schema tool.

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?

A single front-loaded sentence with the action first and the engine list second; there is no filler or repetition. The parenthetical is dense with jargon but each item carries information, so it is appropriately sized for a zero-parameter tool.

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?

For a zero-input tool this covers what it does and the safety/offline profile well. With no output schema, though, the description is the only place an agent could learn what a demo run produces (per-engine pass/fail, report format, result aggregation), and it omits that entirely.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline is 4. The description correctly implies a self-contained call requiring no inputs by noting the vectors are 'embedded.'

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 (Execute) and resource (StarShield's 5 deterministic offline triage engines) and enumerates the five engine domains, so the agent knows this is a bundled all-in-one run. It does not name or contrast itself with the sibling single-engine tools (starshield_inspect_image_tamper, starshield_precheck_leveldb, starshield_validate_financial_iocs), leaving the 'all five at once vs. one at a time' distinction 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description contains no when-to-use, when-not-to-use, or prerequisite guidance. Nothing tells the agent why it would pick this bundled demo over the three sibling tools that cover the same domains individually, nor under what circumstances a demo run is appropriate (e.g., smoke test, capability check).

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