Skip to main content
Glama
Mipiti
by Mipiti

update_organization

Set or reset an organization's target IEC 62443-4-1 maturity level and NIST CSF tier for secure development and cybersecurity risk management.

Instructions

Set per-organization level grades for IEC 62443-4-1 and NIST CSF.

Admin-only: the backend requires the caller to be an admin in the organization (or a superadmin). Non-admins will get a 403; do not invoke this tool unless you've verified admin role for the target org.

target_ml is the IEC 62443-4-1 Maturity Level the organization targets for its secure-development program (1-5). csf_tier is the NIST CSF Tier the organization targets for its cybersecurity risk-management posture (1-4).

Because None on the wire is indistinguishable from "field omitted", pass clear_target_ml=True or clear_csf_tier=True to explicitly reset a value to NULL. Omitting both the value and its clear_* flag leaves the existing server-side value untouched.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
org_idYesOrganization ID.
csf_tierNoNIST CSF Tier (1-4), or ``None`` to leave unchanged.
target_mlNoIEC 62443-4-1 Maturity Level (1-5), or ``None`` to leave unchanged.
clear_csf_tierNoExplicitly reset ``csf_tier`` to NULL.
server_versionYes
clear_target_mlNoExplicitly reset ``target_ml`` to NULL.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations provided, the description fully covers the behavioral aspects: admin requirement, error handling, and the subtle behavior of None vs clear_* flags. It explains that omitting both leaves the server value untouched. Could include more details on idempotency or transaction behavior, but it adequately covers key behavioral traits.

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 well-structured with clear sections. It is concise, front-loads the purpose, and every sentence provides valuable information without redundancy.

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

Completeness4/5

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

Given the presence of an output schema (so return values need not be explained) and the complexity of the parameters, the description covers the main behavioral aspects and parameter semantics well. It could mention whether the update is partial or full replacement, but the clear_* flags imply partial update. Overall, it is fairly complete.

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?

The description adds significant meaning beyond the schema: it explains the distinction between passing None and using clear_* flags, which is critical for correct usage. It also provides the ranges (1-5 for target_ml, 1-4 for csf_tier) not present in the schema. However, the server_version parameter is not described in the description, and its schema lacks a description, leaving a gap.

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 clearly states the tool sets per-organization level grades for IEC 62443-4-1 and NIST CSF, specifying the verb 'Set' and the resource 'organization'. It distinguishes from siblings by focusing on organization-level framework updates, which is unique among the listed sibling tools.

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?

Explicitly states the admin-only requirement and the 403 error for non-admins, providing a clear usage condition. Also explains the difference between setting values and using clear_* flags to reset to NULL. Does not explicitly list alternatives, but the context makes it clear this is the dedicated tool for this task.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Mipiti/mipiti-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server