Skip to main content
Glama
Sign In
ticket-precedent

ticket-precedent

by bondie
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ticket-precedent

No user-submitted related servers found.

    Related Servers

    • jira-kb

      abraganca-1977
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-capable AI assistants to search and retrieve past Jira issues, resolutions, and recurring topics from a fully local embedded knowledge base using hybrid semantic and keyword search.
      MIT

    • github-rag-mcp

      Liplus-Project
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to search and retrieve context from GitHub issues, pull requests, releases, and documentation using hybrid semantic search and time-ordered activity scans.
      233 npm
      Apache 2.0

    • mcp-mantis

      gcorroto
      A
      license
      A
      quality
      D
      maintenance
      Provides AI assistants with direct access to MantisBT issue trackers via the REST API, enabling reading, updating, resolving, and semantically searching issues.
      20
      13 npm
      MIT

    • gl

      soham504
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides coding agents with real-time, code-aware functionality to locate relevant files and search code within a repository based on bug reports or queries.
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    B3.4/5.0

    Scored across 4 tools

    Disambiguation4/5

    similar_tickets and precedents_for both retrieve prior tickets, but the descriptions clearly distinguish free-text search from ticket-key-driven precedent lookup. get_ticket and list_sources are cleanly separate, so agents should usually pick correctly despite the overlap.

    Naming Consistency3/5

    The names are readable and all snake_case, but conventions are mixed: get_ticket and list_sources are verb_noun, similar_tickets is adjective_noun, and precedents_for is noun_preposition. There is no single predictable pattern across the four tools.

    Tool Count5/5

    Four tools is well-scoped for a ticket precedent retrieval server: source discovery, text similarity search, ticket-relative precedent lookup, and full ticket retrieval. Each tool has a clear role and none feels redundant.

    Completeness4/5

    The surface covers source discovery, both major search modes, and full ticket retrieval, which is solid for the apparent retrieval-focused domain. A minor gap is the lack of an explicit index refresh/sync operation or project listing, though list_sources partly mitigates this.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources