Skip to main content
Glama
dearlordylord

Huly MCP

by dearlordylord
OverviewSchemaRelated ServersScoreDiscussions
TypeScript

invoke_tool

Destructive

Call any Huly operation directly by exact name and arguments, supporting both read and write actions through the proxy.

Instructions

Invokes one proxy-visible Huly tool by exact name with its arguments. This tool can call read or write Huly operations; check get_tool_schema and the target tool annotations when safety matters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolNameYesExact Huly tool name to invoke through the proxy.
argumentsNoArguments object for the target Huly tool. Use {} when the target tool accepts no parameters.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
warningsNoOptional agent-visible warnings about degraded result fidelity or important operational conditions. Omitted when there is nothing the agent needs to surface.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed6 schema fields changedv0.44.6
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / properties / result / properties / result / title
      Removed value: -"unknown"
    • removedOutput schema / properties / result / properties / toolName / $ref
      Removed value: -"#/$defs/ToolName"
    • addedOutput schema / properties / result / properties / toolName / allOf
      Added value: +[
+  {
+    "$ref": "#/$defs/ToolName"
+  }
+]
    • addedOutput schema / properties / result / properties / toolName / description
      Added value: +"Exact MCP tool name registered by this server."
    • removedOutput schema / properties / result / properties / warnings / items
      Removed value: -{
-  "title": "unknown"
-}
  2. Changed1 schema field changedv0.44.5
    • changedOutput schema / properties / warnings / items / properties / code / enum
      Previous value: -[
-  "status_metadata_unresolved",
-  "space_role_assignments_degraded",
-  "message_template_metadata_degraded",
-  "viewlet_descriptor_metadata_degraded",
-  "space_preference_metadata_degraded",
-  "approval_request_person_metadata_degraded",
-  "approval_request_count_metadata_degraded",
-  "hosted_huly_shutdown",
-  "issue_label_metadata_degraded",
-  "issue_milestone_metadata_degraded",
-  "notification_metadata_degraded",
-  "card_version_metadata_degraded",
-  "issue_creator_metadata_degraded",
-  "recruiting_review_metadata_degraded",
-  "issue_relation_metadata_degraded",
-  "class_collaborator_metadata_degraded",
-  "external_channel_runtime_unsupported"
-]New value: +[
+  "status_metadata_unresolved",
+  "space_role_assignments_degraded",
+  "message_template_metadata_degraded",
+  "viewlet_descriptor_metadata_degraded",
+  "space_preference_metadata_degraded",
+  "approval_request_person_metadata_degraded",
+  "approval_request_count_metadata_degraded",
+  "hosted_huly_shutdown",
+  "issue_label_metadata_degraded",
+  "issue_milestone_metadata_degraded",
+  "notification_metadata_degraded",
+  "card_version_metadata_degraded",
+  "issue_creator_metadata_degraded",
+  "recruiting_review_metadata_degraded",
+  "issue_relation_metadata_degraded",
+  "class_collaborator_metadata_degraded",
+  "external_channel_runtime_unsupported",
+  "support_runtime_unsupported",
+  "support_status_metadata_degraded",
+  "workbench_navigation_metadata_degraded"
+]
  3. Changed1 schema field changedv0.44.4
    • changedOutput schema / properties / warnings / items / properties / code / enum
      Previous value: -[
-  "status_metadata_unresolved",
-  "space_role_assignments_degraded",
-  "message_template_metadata_degraded",
-  "viewlet_descriptor_metadata_degraded",
-  "space_preference_metadata_degraded",
-  "approval_request_person_metadata_degraded",
-  "approval_request_count_metadata_degraded",
-  "hosted_huly_shutdown",
-  "issue_label_metadata_degraded",
-  "issue_milestone_metadata_degraded",
-  "notification_metadata_degraded",
-  "card_version_metadata_degraded",
-  "issue_creator_metadata_degraded"
-]New value: +[
+  "status_metadata_unresolved",
+  "space_role_assignments_degraded",
+  "message_template_metadata_degraded",
+  "viewlet_descriptor_metadata_degraded",
+  "space_preference_metadata_degraded",
+  "approval_request_person_metadata_degraded",
+  "approval_request_count_metadata_degraded",
+  "hosted_huly_shutdown",
+  "issue_label_metadata_degraded",
+  "issue_milestone_metadata_degraded",
+  "notification_metadata_degraded",
+  "card_version_metadata_degraded",
+  "issue_creator_metadata_degraded",
+  "recruiting_review_metadata_degraded",
+  "issue_relation_metadata_degraded",
+  "class_collaborator_metadata_degraded",
+  "external_channel_runtime_unsupported"
+]
  4. Changed1 schema field changedv0.44.3
    • changedOutput schema / properties / warnings / items / properties / code / enum
      Previous value: -[
-  "status_metadata_unresolved",
-  "space_role_assignments_degraded",
-  "message_template_metadata_degraded",
-  "viewlet_descriptor_metadata_degraded",
-  "space_preference_metadata_degraded",
-  "approval_request_person_metadata_degraded",
-  "approval_request_count_metadata_degraded",
-  "hosted_huly_shutdown"
-]New value: +[
+  "status_metadata_unresolved",
+  "space_role_assignments_degraded",
+  "message_template_metadata_degraded",
+  "viewlet_descriptor_metadata_degraded",
+  "space_preference_metadata_degraded",
+  "approval_request_person_metadata_degraded",
+  "approval_request_count_metadata_degraded",
+  "hosted_huly_shutdown",
+  "issue_label_metadata_degraded",
+  "issue_milestone_metadata_degraded",
+  "notification_metadata_degraded",
+  "card_version_metadata_degraded",
+  "issue_creator_metadata_degraded"
+]
  5. Changed2 schema fields changedv0.44.2
    • changedOutput schema / properties / warnings / description
      Previous value: -"Optional agent-visible warnings about degraded result fidelity. Omitted when the server returned the documented happy-path payload."New value: +"Optional agent-visible warnings about degraded result fidelity or important operational conditions. Omitted when there is nothing the agent needs to surface."
    • changedOutput schema / properties / warnings / items / properties / code / enum
      Previous value: -[
-  "status_metadata_unresolved",
-  "space_role_assignments_degraded",
-  "message_template_metadata_degraded",
-  "viewlet_descriptor_metadata_degraded",
-  "space_preference_metadata_degraded",
-  "approval_request_person_metadata_degraded",
-  "approval_request_count_metadata_degraded"
-]New value: +[
+  "status_metadata_unresolved",
+  "space_role_assignments_degraded",
+  "message_template_metadata_degraded",
+  "viewlet_descriptor_metadata_degraded",
+  "space_preference_metadata_degraded",
+  "approval_request_person_metadata_degraded",
+  "approval_request_count_metadata_degraded",
+  "hosted_huly_shutdown"
+]
  6. Addedv0.44.0

TDQS

A4.2/5.0
Behavior4/5

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

The description discloses that the tool can perform both read and write operations and recommends reviewing target tool annotations, adding nuance beyond the binary destructiveHint annotation. The safety guidance is actionable and does not contradict annotations.

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?

Two sentences clearly state the core purpose and safety considerations without wasted words. The description is front-loaded and easy to scan.

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?

The description covers essential aspects: what the tool does, how to invoke it safely, and parameter usage is handled by the schema. Since an output schema exists, omitting return-value details is acceptable.

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 description coverage is 100%, so the schema already documents both toolName and arguments thoroughly. The description adds minimal extra meaning beyond using the phrase 'exact name', but with full schema coverage this is acceptable.

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 invokes a proxy-visible Huly tool by exact name with arguments, using a specific verb and resource. This distinguishes it from siblings like get_tool_schema or search_tools, making its purpose unambiguous.

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?

The description mentions the tool can call read or write operations and advises checking get_tool_schema and target annotations when safety matters. This provides useful context for when to use it, though it could more explicitly contrast with alternative tools.

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/dearlordylord/huly-mcp'

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