Skip to main content
Glama

update_organisation_defaults

DestructiveIdempotent

Replace organisation-wide default input and output guardrail lists so non-excluded workspaces inherit updated enforcement; only supplied directions change. Inspect defaults and exclusions first.

Instructions

Replace the organisation-wide default input and/or output guardrail lists inherited by workspaces. Only supplied directions change, but enforcement updates immediately across non-excluded workspaces; inspect get_organisation_defaults and the directional workspace exclusions first. Repeating the same lists is safe. Requires an organisation service API key with organisation_settings.update scope. Enterprise-gated. Returns 403 on non-Enterprise Portkey plans.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "update_organisation_defaults"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_guardrailsNoOrdered guardrail IDs or slugs to enforce on model input
output_guardrailsNoOrdered guardrail IDs or slugs to enforce on model output

Output Schema

NameRequiredDescriptionDefault
okYesCall succeeded
dataNoSuccess payload
errorNoFailure details

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.16.5
    • changedOutput schema / properties / data / description
      Previous value: -"Structured success payload when ok is true"New value: +"Success payload"
    • changedOutput schema / properties / error / description
      Previous value: -"Structured error payload when ok is false"New value: +"Failure details"
    • changedOutput schema / properties / error / properties / details / description
      Previous value: -"Optional structured error details"New value: +"Extra error details"
    • changedOutput schema / properties / error / properties / message / description
      Previous value: -"Human-readable error message"New value: +"Error message"
    • changedOutput schema / properties / ok / description
      Previous value: -"Whether the tool call succeeded and returned structured data"New value: +"Call succeeded"
  2. Changed2 schema fields changedv1.0.9
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only flag destructive/idempotent/open-world; the description adds substantive context beyond them: partial replacement semantics, immediate propagation across non-excluded workspaces, idempotency rationale ('repeating the same lists is safe'), required API key scope (organisation_settings.update), Enterprise gating, and a concrete 403 failure mode. Nothing here contradicts the destructive/idempotent hints.

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?

The mutation and its blast radius are front-loaded in the first two sentences, followed by safety, then auth/gating. Small redundancy between 'Enterprise-gated' and 'Returns 403 on non-Enterprise Portkey plans', but the rest earns its place.

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 2-param org-wide mutation with an output schema, the definition covers what changes, who it affects, prerequisites, idempotency, credentials, and the entitlement failure mode. An agent has everything needed to call it correctly or avoid calling it.

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%, so both parameters are already documented, but the description adds meaning the schema does not: omitting a direction leaves that direction untouched, and the lists are enforced per-direction with immediate effect. That raises it slightly above the baseline 3 without adding format or ordering syntax detail.

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 a specific verb+resource: 'Replace the organisation-wide default input and/or output guardrail lists inherited by workspaces.' It explicitly names get_organisation_defaults and the workspace-exclusion tools as the read-side counterparts, so an agent can separate this mutation from its sibling readers without opening schemas.

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

Usage Guidelines4/5

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

It gives clear preconditions — inspect get_organisation_defaults and directional workspace exclusions first — and clarifies partial-update semantics ('only supplied directions change'). It does not, however, distinguish this org-default tool from the tenant-level update_guardrail or the exclusion-update tools, leaving one plausible sibling ambiguity unresolved.

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