Skip to main content
Glama

validate

Verifies artifacts by module and action, checking PE signatures, table schemas, and format templates against sample files.

Instructions

Validate artifacts. Dispatches by module+action.

Modules/actions: pe: verify_signature (path, signature) tables: validate (path, schema) format: validate_template (template_path, sample_files)

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": {
      "module": "<module>",
      "action": "<action>"
    },
    "name": "validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
moduleYes
paramsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

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?

With no annotations, the description carries the full burden, and it does disclose the key non-obvious behavior: this is a polymorphic dispatcher keyed on module+action. It says nothing about whether validation mutates state, what permissions or file access it needs, or how failures are reported, which matters for a tool that reads paths from disk.

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?

A single scope sentence followed by a compact, front-loaded table of module/action/param tuples. No filler, and the most decision-relevant information (the dispatch keys) comes first.

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?

The output schema is declared, so return values need not be explained. For a three-way dispatcher with no annotations, though, the description leaves real gaps: whether params are required per action, what validation rules each module applies, and how invalid module/action values are handled.

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 coverage is 0%, so the description must compensate, and it does: it enumerates the valid module values (pe, tables, format), their action values, and the concrete param names each action takes (path/signature, path/schema, template_path/sample_files). What is missing is per-param meaning, types, and which of those params are required versus optional.

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?

"Validate artifacts" gives a specific verb+resource, and the module/action table makes the dispatcher's purpose concrete (signature verification, table schema validation, template validation). It stops short of saying what 'artifacts' are in this domain or how it differs from the sibling 'diagnose' or 'inspect'.

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?

The module/action list effectively tells the agent which combinations are callable, which is the core usage decision for this tool. However, there is no guidance on when to prefer validate over siblings like diagnose or inspect, and no statement of prerequisites or what to do when a module/action pair is not listed.

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