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

huly-mcp-selfhost

by JoKeks2023
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_person

Read-only

Fetch person details, channels, and organizations by name or ID to resolve contacts and team relationships in Huly.

Instructions

Person details, channels, organizations

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": {
      "person": "<person>"
    },
    "name": "get_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
personYesPerson name or id
workspaceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.5.1

TDQS

D1.9/5.0
Behavior2/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 externally. The description adds nothing behavioral beyond that — no note on what is returned when the person is missing, whether channels/organizations are truncated, or whether workspace scoping changes results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

Brevity here is under-specification rather than economy — three comma-separated nouns with no sentence structure or front-loaded purpose. There is no wasted wording, but there is also no usable content to structure.

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

Completeness1/5

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

For a tool with a required identifier parameter and an undocumented optional scope parameter, and with no output schema, the description leaves the agent without the minimum needed to call it correctly. The relationship between 'person' and 'workspace' is entirely unexplained.

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 50%: 'person' is documented as name or id, while 'workspace' has no description anywhere. The description mentions neither parameter, so it does not compensate for the undocumented workspace filter or clarify name-vs-id resolution behavior.

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

Purpose2/5

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

The description is a bare noun fragment, 'Person details, channels, organizations', which essentially restates the tool name rather than stating a verb+resource. It does hint that the result includes related channels and organizations, but an agent gets no confirmation of what retrieval actually means here.

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?

There is no when-to-use guidance, no mention of when not to use it, and no reference to siblings such as get_organization or create_person. The agent must infer that this is the read path for a single person from the name alone.

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