Skip to main content
Glama

Related Servers

Alternatives to pta-auto-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables automated access to problems, contests, solutions, and public or authenticated user data across global and China platforms, with tools for searching problems, retrieving profiles and submissions, running code, submitting solutions, and managing notes.
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables LLMs to browse and retrieve tasks from the FIPI EGE open bank, including subject listing, task search with metadata and LaTeX-formatted conditions, and automated answer checking for short-answer questions.
      4
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to crawl and extract data from Chinese social media platforms like Bilibili, Xiaohongshu, and Douyin. Provides search, content detail retrieval, and creator information tools with persistent browser sessions and QR code login support.
      78
      -

    TDQS

    A3.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool maps to a distinct step in the exam workflow: login, list exams, pull problem set, submit answers, view submission detail. The descriptions make the boundary between pta_list_exams (exam_id discovery) and pull_exam_set (problem content retrieval) explicit, so no overlap remains.

    Naming Consistency3/5

    All names are snake_case, but prefixing is inconsistent: pta_login, pta_list_exams, and pta_submission_detail carry the pta_ prefix while pull_exam_set and submit_answers do not. The verb_noun style is mostly respected but pta_submission_detail drops the verb entirely.

    Tool Count5/5

    Five tools is a tight, well-scoped set that mirrors the end-to-end task of logging in, finding an exam, pulling problems, submitting, and reviewing results. Each tool clearly earns its place with no redundancy.

    Completeness4/5

    The core lifecycle (auth, discovery, retrieval, submission, result inspection) is fully covered, so agents can complete the primary workflow. Minor gaps like logout or listing all past submissions exist but agents can work around them using returned submission_ids.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues