Skip to main content
Glama

Create integration config

init_integration_config

Creates a starter .qa-mcp/integration.yaml and optional example test flow so teams can begin authoring end-to-end integration tests.

Instructions

Write a starter .qa-mcp/integration.yaml and, optionally, tests/integration/example.yaml.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "init_integration_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
overwriteNo
example_flowNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, and it discloses almost nothing beyond the write itself. It does not say what happens when the target files already exist, what the overwrite flag does (default false suggests files are preserved, but that must be inferred), what is returned, or whether the directory must exist beforehand.

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?

A single front-loaded sentence with no filler; it names the primary output first and the conditional output second. Nothing could be removed without losing content.

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?

For a filesystem-mutating tool with no annotations and no output schema, the definition omits the two behaviors an agent most needs: overwrite semantics and how example_flow maps to the optional file. The core action is covered, but the operational details that determine a safe, correct call are absent.

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?

Schema description coverage is 0% for both parameters, so the description must compensate and largely fails to. "Optionally" hints that example_flow toggles the example.yaml file, but the overwrite parameter is never mentioned at all and no parameter meaning is stated beyond that one implication.

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 concrete verb ("Write") and the exact artifacts produced (.qa-mcp/integration.yaml and tests/integration/example.yaml), so the agent knows precisely what calling it creates. It does not distinguish itself from siblings like integration_config or validate_flow, leaving the boundary implicit.

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

Usage Guidelines3/5

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

"starter" implies scaffolding or first-time setup, which is the only usage signal given. There is no explicit when-to-use, when-not-to-use, or named alternative for regenerating or editing an existing config.

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