Skip to main content
Glama

Fixter

by dev.fixter.mcp
OverviewDiscussionsAdmin

Set Issue Digest Config

set_issue_digest_config
DestructiveIdempotent

Change this account's issue digest. Admin only. Only the fields you pass change; every other field keeps its stored value, so read get_issue_digest_config first when the request depends on them. An enabled digest needs a channel, passed now or already stored: it posts to that one Slack channel and nowhere else. When the user named no channel and none is stored, ask which channel instead of picking one. Returns the saved digest.

Input Schema

NameRequiredDescriptionDefault
daysNoThe days it is sent, as MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SATURDAY or SUNDAY; at least one when enabled. Omit to keep them.
channelNoThe Slack channel id it posts to, such as C0123ABCD: the channelId of a list_alert_channels entry, never its id. An empty string clears it, which only a disabled digest allows. Omit to keep it.
enabledNotrue sends the digest, false stops it. Omit to keep it as it is.
hourUtcNoThe hour it is sent, 0 to 23, in UTC: convert a local time to UTC first. Omit to keep it.
maxItemsNoThe most issues it lists, 1 to 15. Omit to keep it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • addedInput schema / properties / channel
      Added value: +{
+  "description": "The Slack channel id it posts to, such as C0123ABCD: the channelId of a list_alert_channels entry, never its id. An empty string clears it, which only a disabled digest allows. Omit to keep it.",
+  "type": "string"
+}
    • addedInput schema / properties / days
      Added value: +{
+  "description": "The days it is sent, as MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SATURDAY or SUNDAY; at least one when enabled. Omit to keep them.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • removedInput schema / properties / deliveryChannelId
      Removed value: -{
-  "description": "Slack channel id to deliver the digest to. Omit to keep the current value.",
-  "type": "string"
-}
    • addedInput schema / properties / enabled
      Added value: +{
+  "description": "true sends the digest, false stops it. Omit to keep it as it is.",
+  "type": "boolean"
+}
    • addedInput schema / properties / hourUtc
      Added value: +{
+  "description": "The hour it is sent, 0 to 23, in UTC: convert a local time to UTC first. Omit to keep it.",
+  "format": "int32",
+  "type": "integer"
+}
    • removedInput schema / properties / lookbackDays
      Removed value: -{
-  "description": "Number of days to look back when generating the digest. Omit to keep the current value.",
-  "format": "int32",
-  "type": "integer"
-}
    • addedInput schema / properties / maxItems
      Added value: +{
+  "description": "The most issues it lists, 1 to 15. Omit to keep it.",
+  "format": "int32",
+  "type": "integer"
+}
    • removedInput schema / properties / mode
      Removed value: -{
-  "description": "Digest mode: OFF, INTERNAL, or LIVE. Omit to keep the current mode.",
-  "type": "string"
-}
    • removedInput schema / properties / scheduleCron
      Removed value: -{
-  "description": "Cron expression for the digest schedule. Omit to keep the current value.",
-  "type": "string"
-}
    • removedInput schema / properties / scheduleTimezone
      Removed value: -{
-  "description": "Timezone for the schedule (e.g. UTC). Omit to keep the current value.",
-  "type": "string"
-}
    • removedInput schema / properties / splitMessages
      Removed value: -{
-  "description": "Post each surfaced issue as its own Slack message instead of one combined digest (for message-based integrations like Linear's Slack bot). Omit to keep the current value.",
-  "type": "boolean"
-}
  2. Changed3 schema fields changed
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / lookbackDays / format
      Added value: +"int32"
  3. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond annotations that already declare destructive, idempotent, and non-read-only behavior, the description adds admin authorization, partial-update semantics ('only the fields you pass change'), the cross-field requirement that an enabled digest needs a channel, and the single-Slack-channel posting side effect.

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?

The description is compact and front-loaded with the action and admin restriction. Every sentence carries operational guidance: partial update, read-before-write, channel precondition, ask-user fallback, and return value.

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?

Given five optional parameters, full schema coverage, existing annotations, and no output schema, the description supplies the missing operational context. It covers admin-only access, partial update behavior, channel requirements, user-interaction guidance, and what is returned.

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 description coverage is 100%, so per-parameter meaning is already well supplied. The description adds valuable cross-field and stored-state semantics, such as an enabled digest needing a channel passed now or already stored, but most field-level detail remains schema-driven.

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 mutation action and resource: 'Change this account's issue digest.' It distinguishes the tool from its read sibling by telling the agent to read get_issue_digest_config first when stored values matter, and the admin-only constraint further narrows its purpose.

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?

Provides explicit operational routing: read get_issue_digest_config first when the request depends on stored values, and ask the user for a channel instead of picking one when none is named or stored. It also establishes the admin-only precondition and partial-update behavior.

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

All Fixter toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources