Skip to main content
Glama
Sign In

Kaiku

by tech.kaiku.mcp
OverviewDiscussionsAdmin

Set Jira connection

set_jira_connection
Destructive

Switch a project's Jira connection on or off, keeping its token — and, with 'confluence', whether the same site's Confluence is read too. Off, nothing reads that Jira or writes to it — the issue screen, the agents, the status sync — and issues keep their keys there. Switched on, the held token is asked of the site first and refused with the site's reason if it no longer opens it. Connecting a Jira, or giving a new token — Confluence's own included — is done on the board's Jira sheet (get_jira_connection's 'url'), never here. For whoever administers the project.

Input Schema

NameRequiredDescriptionDefault
enabledNotrue to switch the connection on, false to switch it off. Leave out to keep it as it is.
confluenceNotrue to read the same site's Confluence too, false to stop. Leave out to keep it as it is.
projectKeyYesProject key, e.g. 'PM'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / confluence
      Added value: +{
+  "default": null,
+  "description": "true to read the same site's Confluence too, false to stop. Leave out to keep it as it is.",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
    • addedInput schema / properties / enabled / default
      Added value: +null
    • changedInput schema / properties / enabled / description
      Previous value: -"true to switch it on, false to switch it off."New value: +"true to switch the connection on, false to switch it off. Leave out to keep it as it is."
    • changedInput schema / properties / enabled / type
      Previous value: -"boolean"New value: +[
+  "boolean",
+  "null"
+]
    • changedInput schema / required
      Previous value: -[
-  "projectKey",
-  "enabled"
-]New value: +[
+  "projectKey"
+]
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: it spells out the blast radius of turning off (issue screen, agents, status sync stop reading/writing) and the non-destructive side effect (issue keys are preserved). It also discloses that enabling re-validates the held token against the site and surfaces the site's refusal reason, which is exactly the failure mode an agent needs to anticipate. Consistent with destructiveHint=true and openWorldHint=true.

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?

Front-loaded with the toggle and the token-preservation guarantee, and every clause carries information. The em-dash-heavy phrasing is denser than necessary — 'Off, nothing reads that Jira or writes to it — the issue screen, the agents, the status sync —' could be tightened — but nothing is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive admin toggle with full annotation coverage, 100% schema descriptions and no output schema, the description supplies everything missing: consequences of both directions, token retention, validation-on-enable, and where the out-of-scope operations live.

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?

Schema coverage is 100% (baseline 3), and the description adds real semantics on top: the token is retained across the switch, and 'confluence' means reading the *same site's* Confluence. It reinforces that omitting a flag leaves state unchanged. It doesn't add format-level detail, but little is needed for two booleans.

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?

States a specific verb and resource ('switch a project's Jira connection on or off') and immediately scopes what the toggle governs, including the 'confluence' sub-behavior. It explicitly distinguishes itself from get_jira_connection and from the board's Jira sheet, which handles connecting and new tokens.

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

Usage Guidelines5/5

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

Gives a hard exclusion ('Connecting a Jira, or giving a new token ... is done on the board's Jira sheet (get_jira_connection's "url"), never here') and names the sibling that owns that job. It also states the audience ('For whoever administers the project'), so an agent knows the required authority level.

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

All Kaiku toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources