Skip to main content
Glama

Integration config

integration_config

Retrieves the integration setup for k11 Integration QA, including brokers, jobs, AsyncAPI contracts, protected topics, environments, and test flows to guide end-to-end test configuration.

Instructions

Brokers, jobs, AsyncAPI contract, protected topics, environments (and whether publishing and jobs may run there) and the flows found under tests/integration/.

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": "integration_config"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/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 behavioral burden, yet it never says whether this is a read-only retrieval, what form the returned data takes, or whether it hits live broker/environment state. The parenthetical hint that environments indicate whether publishing and jobs may run there is the only behavioral signal.

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?

It is short with no filler, but it is a fragment without a predicate, so brevity comes at the cost of clarity. The list is not front-loaded around any outcome or return value.

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?

With no annotations, no output schema, and no parameters, the description is the only source of information, and it omits what the tool returns, in what shape, and at what scope. For a zero-arg configuration reader that is a substantial gap.

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

Parameters4/5

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

The tool takes zero parameters, so the schema imposes no semantic burden and the baseline of 4 applies. The description's parenthetical about environments is a small extra interpretive note rather than parameter documentation.

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

Purpose2/5

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

The text is a bare noun phrase enumerating data categories (brokers, jobs, AsyncAPI contract, protected topics, environments, flows under tests/integration/) with no verb indicating what the tool actually does. An agent must infer that it retrieves that configuration, and nothing distinguishes it from init_integration_config except the name.

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 when-to-use guidance, no prerequisites, and no mention of init_integration_config, run_integration_tests, or validate_flow as alternatives. The implied usage (read the integration setup) is left entirely to inference.

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