Skip to main content
Glama

validate_dctl

Read-only

Checks DCTL source code for compile errors, returning the error text when invalid or null when the code is valid.

Instructions

Compile-check DCTL source code. Returns null when valid, otherwise the error text.

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": {
      "source": "<source>"
    },
    "name": "validate_dctl"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, openWorldHint=false), and the description adds real value by disclosing the return convention: null on success, error text on failure, which stands in for the absent output schema. It doesn't state whether the check is syntax-only versus full compile semantics or how errors are formatted beyond 'error text'.

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 short sentences, purpose front-loaded, return behavior second. No filler or 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?

For a one-parameter read-only utility, purpose plus return contract is nearly all an agent needs, and the missing output schema is compensated by the stated null/error result. Minor gaps remain around error payload structure and validation depth.

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 0% and the single `source` parameter is undocumented in the schema; the description implies it is DCTL source text but says nothing about format, size limits, or whether partial snippets are accepted. It adds marginal meaning over the bare schema.

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?

Names a specific verb+resource ('Compile-check DCTL source code'), which is concrete enough to tell apart from something like encrypt_dctl. It doesn't explicitly reference siblings, but the action is unambiguous.

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?

No when-to-use or when-not-to-use guidance, and no mention of a natural alternative such as encrypt_dctl or any prerequisite step. The agent must infer that this is a pre-flight check.

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