Skip to main content
Glama

integration_config

Read-onlyIdempotent

Generates a version-pinned local configuration for an official AWS server or a remote Knowledge config, without installing, starting, or approving tools.

Instructions

Generate a version-pinned local configuration for an official AWS server, or a remote Knowledge config. Does not install, start or approve tools.

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": {
      "serverId": "<serverId>"
    },
    "name": "integration_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNous-east-1
serverIdYes
awsProfileNoyour-readonly-profile

Output Schema

NameRequiredDescriptionDefault
nextNo
pythonNo
sourceNo
statusNo
warningNo
configurationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • changedInput schema / required
      Previous value: -[
      -  "serverId",
      -  "awsProfile",
      -  "region"
      -]New value: +[
      +  "serverId"
      +]
  2. First observedv0.4.1

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered; the description adds useful scope framing that generation has no install/approve side effects. It leaves key behavioral ambiguity: 'version-pinned' suggests a version is selected, yet no version parameter exists, and it does not say whether the config is returned or written to disk.

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?

Two short sentences, front-loaded with the primary action and followed immediately by the scope exclusion, with no filler. The phrase 'or a remote Knowledge config' is slightly cryptic but not wasteful.

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?

The output schema covers return values, but for a three-parameter tool with zero schema coverage and two distinct generation modes, the description is materially incomplete. An agent cannot determine from the definition which parameters select which mode, where the pinned version comes from, or how awsProfile is used.

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% — serverId, region, and awsProfile have no property descriptions at all, and the description adds no meaning for any of them. It never explains what a 'serverId' identifies, that region scopes the AWS endpoint, or that awsProfile supplies credentials, despite the placeholder default 'your-readonly-profile'. With three undocumented parameters, the description should compensate and does not.

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?

A specific verb-plus-resource statement: 'Generate a version-pinned local configuration' with two modes (official AWS server vs. remote Knowledge config). An agent can tell it produces config rather than deploying it. It stops short of a 5 because the two modes are not tied to any parameter or sibling, so the agent cannot tell which mode it will get from a given call.

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?

The negative scope 'Does not install, start or approve tools' implicitly tells the agent to look elsewhere for deployment or approval, which is genuine routing signal. However, no sibling is named — including integration_catalog, mcp_config_review, or aws_skill — so the when-to-use-this-vs-alternative decision is left to inference.

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