Skip to main content
Glama

neuron

by io.github.conquext
OverviewDiscussionsAdmin

Update Organization

neuron_update_organization
Idempotent

Update organization settings such as name, description, or configuration preferences. Only provided fields are changed.

Input Schema

NameRequiredDescriptionDefault
nameNoNew display name for the organization
orgIdYesUnique identifier (UUID) of the organization to update
timezoneNoIANA timezone such as Asia/Almaty or Africa/Lagos. Bots use it for today's date and listing expiry ends at midnight in it. Null resets to Africa/Lagos.
autoOptOutBroadcastNoAuto-exclude a contact from broadcasts when they send a broadcast opt-out message (e.g. 'stop messaging me'). Off by default.
autoSuppressHostileNoAuto-exclude a contact from broadcasts when they are hostile about being contacted (e.g. cursing us out for messaging them). Off by default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / timezone
      Added value: +{
+  "description": "IANA timezone such as Asia/Almaty or Africa/Lagos. Bots use it for today's date and listing expiry ends at midnight in it. Null resets to Africa/Lagos.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / autoOptOutBroadcast
      Added value: +{
+  "description": "Auto-exclude a contact from broadcasts when they send a broadcast opt-out message (e.g. 'stop messaging me'). Off by default.",
+  "type": "boolean"
+}
    • addedInput schema / properties / autoSuppressHostile
      Added value: +{
+  "description": "Auto-exclude a contact from broadcasts when they are hostile about being contacted (e.g. cursing us out for messaging them). Off by default.",
+  "type": "boolean"
+}
  3. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare this is a non-read, idempotent, non-destructive mutation, so the safety profile is covered. The description adds genuinely new information beyond that: 'Only provided fields are changed' discloses PATCH-style semantics, meaning unspecified settings are preserved. It omits any auth/permission requirement, so it falls short of a 5.

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?

Two short sentences, front-loaded with the action and immediately followed by the one behavioral caveat. Every sentence earns its place with no filler.

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?

For a straightforward settings-update tool whose params are fully documented and whose safety profile is covered by annotations, the description is adequate but thin: it omits permission requirements, any note about the response, and its field examples do not match the actual schema, which risks mild confusion.

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 the schema already explains every parameter in rich detail (IANA timezones, null reset behavior, default off for the booleans). The description's field list adds no syntax or meaning beyond the schema and even mentions a 'description' field that does not exist, so baseline 3 is appropriate.

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

Purpose4/5

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

States a specific verb+resource ('Update organization settings') and gives example fields, which is enough to tell it apart from the many other neuron_update_* siblings that target different resources. However, the examples are partly inaccurate: the schema exposes name, timezone, and two auto-suppression booleans, but no 'description' field, and 'configuration preferences' is vague.

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?

No when-to-use context, no prerequisites (permissions/role needed to edit an org), and no reference to alternatives such as neuron_get_organization for reading. The only guidance is the partial-update note, which is behavioral rather than a usage condition.

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

All neuron 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