Skip to main content
Glama
Sign In
make-audit-mcp

make-audit-mcp

by koleharv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Inspect a Make blueprint

inspect_blueprint

Overview of a Make.com scenario blueprint before importing it: modules, apps used, trigger, routers, error handlers, scenario settings.

Instructions

Overview of a Make.com scenario blueprint before importing it: modules, apps used, trigger, routers, error handlers, scenario settings.

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": {
      "path": "<path>"
    },
    "name": "inspect_blueprint"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath to a Make.com scenario blueprint (.json export)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It implies a read-only operation ('before importing') but does not explicitly state that it avoids modifications, nor does it describe return format or validation behavior. This is adequate but not rich.

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?

The description is a single, concise sentence that front-loads the purpose and lists key elements. Every word earns its place with no redundancy.

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?

This is a simple one-parameter tool with no output schema. The description covers the tool's purpose and scope adequately. It does not describe the return structure, but 'overview' implies a summary, making it sufficiently complete for its complexity.

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 coverage is 100% and the lone parameter 'path' is already well-described in the schema. The tool description adds no additional parameter meaning, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear, specific purpose: providing an overview of a Make.com scenario blueprint before importing. It enumerates the aspects covered (modules, apps used, trigger, routers, error handlers, scenario settings), which differentiates it from the sibling tools trace_module and audit_blueprint.

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?

The phrase 'before importing it' gives clear contextual timing for when to use this tool. However, it does not explicitly mention alternatives or exclusions, so it earns a 4 rather than a 5.

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

Deploy Server

Other Tools