huly-mcp-selfhost

update_organization

Set an organization's description from Markdown, replacing existing text to keep organizational context accurate and current.

Instructions

Set the description of an organization from Markdown

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace": "<workspace>",
      "organizationId": "<organizationId>",
      "description": "<description>"
    },
    "name": "update_organization"
  }
}

Input Schema

Name	Required	Description
`workspace`	Yes
`description`	Yes	Markdown, replaces existing
`organizationId`	Yes	Organization id

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.5.1Nov 12, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations only declare destructiveHint=false, so the description carries most of the behavioral burden. Saying only 'Set the description' leaves unclear that the existing description is overwritten rather than appended (the schema says 'replaces', the description does not), and says nothing about required permissions, no-op behavior, or whether other organization fields are untouched.

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?

It is a single short sentence with the scope qualifier ('description of an organization') front-loaded and no padding. Its brevity is appropriate, though it tilts toward under-specification rather than waste.

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

Completeness2/5

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

For a 3-required-parameter mutation tool with no output schema and only a destructiveHint=false annotation, the description is too thin. It does not cover the overwrite semantics, the workspace parameter, permission requirements, or what happens to fields other than the description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%; organizationId and description are documented in the schema, but 'workspace' has no description anywhere. The description adds essentially no parameter meaning beyond the schema — 'from Markdown' duplicates the schema's 'Markdown, replaces existing' note — and does not explain what the workspace identifier scopes.

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?

The description names a specific verb and field ('Set the description') on a specific resource ('an organization'), which usefully narrows a tool whose name ('update_organization') suggests broader mutation. It does not differentiate against sibling tools, but the resource qualifier alone makes it distinguishable enough to select.

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 description gives no indication of when to use this tool versus create_organization, get_organization, or the other update_* siblings, and states no prerequisites or preconditions. An agent must infer usage purely from the name and resource.

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

Deploy Server