Skip to main content
Glama
Yan-Vi

easy-spec-mcp

by Yan-Vi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

create_util_group

Create an empty utility group in Easy Spec to organize your utilities or predefine a group for later use.

Instructions

Create a new, empty util group. Groups are also created automatically the first time a util is placed in one (create_util's groupName, or set_util_group_name) -- this is only needed to make an empty one exist in advance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
folderNo
projectNoPath to the project root (same folder the side panel connects to). Defaults to the EASYSPEC_PROJECT environment variable if omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.4

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states the creation action and auto-creation context, but does not mention error behavior (e.g., if the group already exists), side effects, or any other operational details. Basic transparency is present but incomplete.

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?

The description is concise and logically structured: it states the action, then explains the auto-creation behavior, then clarifies when this tool is needed. It avoids unnecessary detail while providing essential context.

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 simple creation tool, the description covers the main purpose and usage condition. It does not describe return values or error handling, but no output schema is present and the core context is sufficient for a basic understanding.

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?

Only the 'project' parameter has a schema description; 'name' and 'folder' are undefined. The tool description does not clarify the meaning or format of 'folder' or any constraints on 'name'. Parameter semantics are therefore weak, leaving the agent to guess.

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 clearly states the tool's purpose: creating a new, empty util group. It distinguishes this from automatic group creation, and the verb 'create' precisely indicates the action. The resource and scope are unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly explains when to use the tool: only to create an empty group in advance, since groups are auto-created when placing utils. This gives direct usage guidance and prevents unnecessary calls.

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