Skip to main content
Glama

get_integrations

Retrieve which integrations apply to each of the factory's seven slots, including names, source, and passed-over reasons; optionally scope results to a specific project.

Instructions

Which integration each of the factory's seven slots uses (tickets, review, ci, memory, monitoring, guardrails, runtime): its name and title, whether the factory's choice, the project's own or the built-in default applies (source), and reason when a stored choice was passed over. Pass project to see what applies to that project; leave it out for a builder station's own project, or the factory's choice outside one. Never returns an integration's settings or secrets.

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

Input Schema

NameRequiredDescriptionDefault
projectNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose meaningful behavior: output is scoped to the seven fixed slots, `source` distinguishes factory/project/default resolution, `reason` appears only when a stored choice was passed over, and secrets/settings are excluded. It doesn't state side effects or auth requirements, but those are low-risk for a pure read.

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 content is front-loaded and dense: the enumeration of slots comes first, then the resolution semantics, then the negative boundary. It is a long single sentence, but each clause carries information an agent needs, with no filler.

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 one-parameter read tool with an output schema present, the description covers scope, parameter effect, and the meaning of the notable return fields (`source`, `reason`) plus the explicit exclusion of secrets. Nothing essential is missing, though identifier format for `project` remains unaddressed.

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 0%, and the description does compensate by explaining what `project` means and what omitting it implies (builder station's own project, or factory choice outside one). That's real added meaning, but the accepted format of `project` (name vs id) is never stated, leaving a gap the schema does not fill.

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 names the exact resource (the seven integration slots: tickets, review, ci, memory, monitoring, guardrails, runtime) and exactly what is reported for each (name, title, source, reason). It also draws a line against sibling settings tools by stating it never returns an integration's settings or secrets, so an agent can tell it apart from get_crew_settings without opening a schema.

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?

It explicitly states the calling condition for the single parameter: pass `project` to see what applies to that project, omit it to get the builder station's own project or the factory's choice outside one. That is clear when-to-use guidance, though no sibling alternative is named for overlapping needs.

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