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

huly-mcp-selfhost

by JoKeks2023
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_persons

Read-only

List contact persons and their channels in Huly. Filter by name, restrict results to employees, or target a specific workspace to find the right people.

Instructions

Contact persons with their channels

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": "list_persons"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoName filter
workspaceNo
employeesOnlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.5.1

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is known. The description adds one useful behavioral detail beyond that: results include each person's channels. It says nothing about pagination, default result size, or ordering, which for a list tool with a limit parameter matters.

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?

Six words with no filler, but it is not a structured or front-loaded explanation so much as an under-specified fragment. Brevity here comes at the cost of information rather than from efficient phrasing.

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?

With four parameters, 25% schema coverage, and no output schema, the description needs to carry weight and does not. It omits what employeesOnly does, how the workspace filter scopes results, and how the channel data is shaped in the response.

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 only 25% – query is the sole documented parameter, and workspace and employeesOnly have no descriptions at all. The description adds no meaning for limit, workspace, or employeesOnly, so the most ambiguous flags (particularly the default-false employeesOnly filter) remain unexplained.

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

Purpose3/5

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

The fragment 'Contact persons with their channels' identifies the resource (persons) and mentions that channel data is attached, but it has no verb and reads as a noun phrase. An agent can guess this is a listing operation for contacts, but it cannot distinguish it from siblings like list_members or list_organizations without opening the schema.

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 or when-not-to-use guidance, no mention of the sibling tools that also return people-related data, and no prerequisites. The agent is left to infer usage entirely from the name.

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