Skip to main content
Glama
Sign In
mguttmann

action1-mcp-server

by mguttmann
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update organization settings

action1_update_organization
Destructive

Modify organizational settings by ID. Update the name or description of an organization resource to manage its metadata within the Action1 platform.

Instructions

Update organization settings. Updates settings for an organization specified by its ID. Perm: manage_organizations.

Input Schema

NameRequiredDescriptionDefault
bodyNoRequest body (schema: OrganizationPayload)
org_idNoOrg UUID.
confirmNoRequired to execute. Exact string "YES".
dry_runNoDefault true (preview). Set false to execute.

Output Schema

NameRequiredDescriptionDefault
idNo
nameNo
selfNo
toolNo
typeNo
dry_runNo
would_sendNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv0.6.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / body / properties
      Added value: +{
+  "description": {
+    "description": "Description for My Organization",
+    "type": "string"
+  },
+  "name": {
+    "type": "string"
+  }
+}
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / additionalProperties
      Previous value: -trueNew value: +{}
    • addedOutput schema / properties / description
      Added value: +{}
    • addedOutput schema / properties / dry_run
      Added value: +{}
    • addedOutput schema / properties / id
      Added value: +{}
    • addedOutput schema / properties / name
      Added value: +{}
    • addedOutput schema / properties / self
      Added value: +{}
    • addedOutput schema / properties / tool
      Added value: +{}
    • addedOutput schema / properties / type
      Added value: +{}
    • addedOutput schema / properties / would_send
      Added value: +{}
  2. First observedv0.5.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is carried by structured data. The description adds the authorization requirement (manage_organizations), which is genuinely useful context, but says nothing about the confirm/'YES' plus dry_run preview flow that governs how this destructive mutation actually executes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, but the second ('Updates settings for an organization specified by its ID') repeats the first with no new information. The one genuinely additive fact, the permission requirement, is buried at the end.

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

Completeness3/5

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

An output schema exists and the schema documents all parameters, so the description needn't explain returns. Still, for a destructive, non-idempotent mutation gated behind a confirm string and a default-on dry_run, an agent would benefit from an explicit note on the preview-then-execute sequence, which is absent.

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 100%, so org_id, confirm, dry_run, and the body fields are already documented. The description only echoes that the target is an org ID and adds no syntax, constraints, or guidance on the nested OrganizationPayload body; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource (update organization settings) and ties it to an org ID, so the basic purpose is clear. However, the second sentence largely restates the first, and nothing distinguishes this from sibling update tools such as action1_update_enterprise or action1_update_me.

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

Usage Guidelines2/5

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

The only usage information is the required permission ('Perm: manage_organizations'). There is no guidance on when to use this versus action1_create_organization, action1_update_enterprise, or action1_update_setting, and no mention of prerequisites or exclusions.

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

Deploy Server

Other Tools