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

huly-mcp-selfhost

by JoKeks2023
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

search_issues

Read-only

Search all issues by full text to find matching records fast. Use it to locate issues by keyword when you don't know the project or ID.

Instructions

Full-text search across all issues

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": {
      "query": "<query>"
    },
    "name": "search_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
workspaceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.5.1

TDQS

C2.7/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a safe read operation, so the bar is lower. The description adds that matching is full-text, which tells the agent results are relevance/term based rather than exhaustive. It says nothing about ranking, result caps, or how 'limit' interacts with total matches.

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?

A single front-loaded sentence with zero filler or redundancy. Its brevity is close to under-specification, but nothing is wasted.

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 three undocumented parameters, no output schema, and only a readOnlyHint annotation, the definition leaves the agent guessing about default limits, workspace scoping, and result shape. The single sentence is not sufficient coverage for this tool's surface.

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 description coverage is 0%, so all three parameters (query, limit, workspace) are undocumented in the schema and the description must compensate. It only implies that 'query' is a full-text string and says nothing about 'limit' semantics or how 'workspace' constrains the search.

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 phrase 'full-text search across all issues' gives a specific verb and resource, and 'full-text' signals the matching mechanism rather than structured filtering. However, it does not distinguish this from the sibling 'search' tool or from 'list_issues', and 'all issues' is ambiguous given a 'workspace' parameter that presumably narrows scope.

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 offers no when-to-use guidance, no conditions under which this beats 'search' or 'list_issues', and no prerequisites or exclusions. An agent must infer that this is for keyword matching rather than enumeration.

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