Skip to main content
Glama
Sign In
huly-mcp-selfhost

huly-mcp-selfhost

by JoKeks2023
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_organization

Read-only

Retrieve a company's organization details by ID, including city, linked members, and description, to inspect or use records returned by list_organizations.

Instructions

Organization (company) by id from list_organizations: city, linked members, description

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": {
      "organizationId": "<organizationId>"
    },
    "name": "get_organization"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceNo
organizationIdYesOrganization id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.5.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds value by naming the returned fields (city, linked members, description), which is important given there is no output schema. It does not mention error behavior or permissions, keeping it 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.

Conciseness3/5

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

It is very short and front-loads the resource, but it is written as a telegraphic fragment with no verb, and the trailing field list ('city, linked members, description') is ambiguous without punctuation or wording to mark it as return values.

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?

For a simple two-parameter read tool with no output schema, the description covers the key gaps: what is fetched and what comes back. The only real omission is the workspace parameter's meaning and any failure behavior.

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 coverage is 50%: organizationId is documented in the schema and reinforced by 'by id', but the workspace parameter is undocumented in both schema and description. The description adds no meaning beyond the existing id documentation, so baseline 3 applies.

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 identifies the resource (organization/company) and the retrieval basis (by id), and ties it to the sibling list_organizations, so an agent can distinguish it from listing tools. It lacks an explicit verb, but the intent to fetch a single organization is unmistakable.

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

Usage Guidelines3/5

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

Referencing list_organizations implies this is the follow-up call once an id is known, giving implicit usage context. There is no explicit when-not guidance or statement of what happens for an invalid id, so usage is only inferred.

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