Skip to main content
Glama

Coderbuds

by com.coderbuds
OverviewDiscussionsAdmin

Set Agent Posture Tool

set-agent-posture-tool
Idempotent

Set how loudly the Coderbuds agent speaks to this team — the single control over whether it acts at all. "off" = silent, Coderbuds still measures but never posts. "preview" = record recommendations in Coderbuds without performing or sending them. "quiet" = weekly pulse only, no nudges. "public" = acts in the open, nudges go to the team channel and never to DMs. "direct" = may message engineers directly. There are no per-capability settings: an individual act that needs a human still asks for approval in Slack regardless of posture. Requires team admin permissions; use get-agent-activity-tool to see the current posture and activity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
postureYesoff = silent; preview = recommendations in Coderbuds only; quiet = weekly pulse only; public = nudges in the team channel; direct = may DM engineers.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamYesTeam name.
messageYesHuman-readable confirmation.
postureYesThe posture now in effect.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / posture / description
      Previous value: -"off = silent; quiet = weekly pulse only; public = nudges in the team channel; direct = may DM engineers."New value: +"off = silent; preview = recommendations in Coderbuds only; quiet = weekly pulse only; public = nudges in the team channel; direct = may DM engineers."
    • changedInput schema / properties / posture / enum
      Previous value: -[
-  "off",
-  "quiet",
-  "public",
-  "direct"
-]New value: +[
+  "off",
+  "preview",
+  "quiet",
+  "public",
+  "direct"
+]
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the idempotentHint annotation, the description details exact behavioral outcomes for every enum value: 'off' still measures but never posts, 'preview' records without sending, 'public' never DMs, and human-required actions still ask for approval. It also discloses the team-admin permission requirement, all of which is valuable context not present in annotations.

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 front-loaded with the core purpose, followed by a structured enumeration of the five values, then caveats and prerequisites. Every sentence contributes distinct information, and the organization makes it easy for an agent to scan, even with the density of content.

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 a single enum parameter, an output schema (presumably returning result/status), and idempotence annotation, the description covers everything needed to invoke correctly: permission level, per-value behavior, cross-tool guidance, and the absence of finer-grained controls. No significant context is missing.

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% and the enum values are documented, so the baseline is 3. The description enriches the semantics by clarifying ambiguous terms: 'preview' means 'without performing or sending them', 'public' means 'never to DMs', and 'off' still includes measurement. This adds tangible meaning beyond the schema.

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 opens with 'Set how loudly the Coderbuds agent speaks to this team', a specific verb and resource, and immediately states it is 'the single control over whether it acts at all.' This clearly distinguishes it from the sibling get-agent-activity-tool and any per-capability setters, so an agent can identify its unique role.

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?

The description gives explicit usage context: requires team admin permissions, directs the agent to get-agent-activity-tool for viewing current posture, and warns that there are no per-capability settings. This is effectively a when-to-use, when-not-to-use, and alternative-tool instruction set.

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

All Coderbuds toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources