Skip to main content
Glama
alexeydubinin

HH JIRA MCP Server

set_defence_checked

Mark JIRA issues as reviewed for security compliance by setting the defence checked status. Use this tool to verify portfolio items meet security requirements.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
portfolioYes

Implementation Reference

  • The handler function for the set_defence_checked tool. It retrieves the Jira issue for the given portfolio ID, updates the customfield_32210 with the defense checklist text using get_defense_text(), and returns a success message with the task URL.
    @mcp.tool()
    def set_defence_checked(portfolio: int) -> str:
        try:
            jira_api = get_jira()
            issue = jira_api.issue(f"PORTFOLIO-{portfolio}")
            issue.update(fields={'customfield_32210': [{'value': get_defense_text()}]})
            return "Defence checked for " + get_task_url(issue.key)
        except Exception as e:
            return f"Error: {str(e)}"
  • Helper function that returns the fixed text to be set in the Jira issue's defense field for the set_defence_checked tool.
    def get_defense_text():
        return 'Я проверил портфель на безопасность по "Чеклисту", портфель не несет рисков или согласован с ' \
               'командой Defense.'
  • Helper function that initializes and returns the JIRA client instance used in the set_defence_checked tool.
    def get_jira():
        return JIRA(server=get_host(),
                    basic_auth=(get_user(), get_password()))
  • Helper function that generates the browse URL for a Jira task key, used in the success message of set_defence_checked.
    def get_task_url(task_name):
        host = get_host()
        return f'{host}/browse/{task_name}'
  • The @mcp.tool() decorator registers the set_defence_checked function as an MCP tool.
    @mcp.tool()
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/alexeydubinin/hh-jira-mcp-server'

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