Skip to main content
Glama
Sign In
Construct

Construct

by rtmandreyev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

construct_expand_params

Read-onlyIdempotent

Expands a parameter document into the full v2 scene it defines, or returns validation diagnostics if the document is invalid.

Instructions

The full v2 scene a valid parameter document builds (or its diagnostics when it is not valid).

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": {
      "params": "<params>"
    },
    "name": "construct_expand_params"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

C2.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral context by saying the result is a full v2 scene when the parameter document is valid and diagnostics when it is not, though it does not describe diagnostic format or validation behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short, but the sentence is grammatically awkward and not front-loaded with a clear action. It is concise without being especially clear.

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

Completeness2/5

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

This tool takes a complex nested input and has no output schema or parameter descriptions. The description states the valid/invalid output distinction but leaves the input contract and diagnostic behavior underspecified for an expansion tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter, params, with a nested object schema and 0% schema description coverage. The phrase "parameter document" gives a high-level hint, but the description does not explain the expected structure or semantics of that document.

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

Purpose3/5

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

The description implies a transformation from a parameter document to a full v2 scene or diagnostics, but it is phrased as a fragment rather than a clear verb+resource statement. It does not explicitly distinguish this operation from siblings such as construct_compile or construct_diagnose.

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?

There is no guidance on when to use this tool versus alternatives such as construct_params_template, construct_compile, or construct_diagnose. The valid/invalid output condition is stated, but it is not framed as usage guidance.

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