Skip to main content
Glama

create_test_plan

Creates a test plan in a project. If a plan with the same name exists, returns the existing one to prevent duplicates.

Instructions

Create a test plan in a project. Idempotent: returns existing plan if one with the same name exists (created=false).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectYesa string that will be trimmed
nameYesa string that will be trimmed
descriptionNoDescription

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesThe successful tool result. The same value is also serialized as JSON in the text content for clients that do not read structuredContent.
warningsNoOptional agent-visible warnings about degraded result fidelity. Omitted when the server returned the documented happy-path payload.
Behavior1/5

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

Description claims idempotency, contradicting annotations which set idempotentHint=false. This is a severe inconsistency. No other behavioral details provided.

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 sentences, no redundancy, front-loaded with purpose. Every word earned its place.

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?

Covers main behavior and idempotency. Output schema exists, so return values need not be explained. Missing guidance on required permissions or failure modes, but acceptable for this tool.

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 description coverage is 100%; parameter descriptions are already in schema. Tool description adds no extra parameter meaning beyond idempotency context.

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?

Description clearly states verb 'Create' and resource 'test plan in a project', and adds useful idempotency detail. Distinguishes from siblings like list/delete/update_test_plan.

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?

Idempotency hints at when to use (to ensure existence). Lacks explicit comparison to alternatives like update_test_plan, but sufficient for common scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dearlordylord/huly-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server