Skip to main content
Glama
jianghongcheng

geomed_copilot

by jianghongcheng
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to geomed_copilot

No user-submitted related servers found.

    Related Servers

    • signet-eval

      wandercom
      A
      license
      Not graded
      quality
      A
      maintenance
      Deterministic policy enforcement for AI agent tool calls. It evaluates every tool call against user-defined rules before execution, with no LLM in the authorization path.
      3
      MIT

    • medmcp

      GattaniAkshit
      F
      license
      A
      quality
      B
      maintenance
      Enables language models to query a clinical relational database through a small set of validated, row-capped tools, with evaluation of answerability and data leakage.
      4
      -

    • Dvarapala

      demolished-lab
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides permission gates and tamper-evident audit logging for AI agent tool executions, with declarative policies, consent ladders, and hash-chained verification.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool serves a clearly distinct purpose: describing backend capabilities, listing available cases, and analyzing a specific radiograph. There is no overlap in functionality, making misselection unlikely.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: list_geomed_capabilities, list_available_cases, analyze_radiograph. The naming is uniform and predictable.

    Tool Count5/5

    With only 3 tools, the set is tightly scoped for the stated purpose of interacting with a GeoMed backend for case analysis. Each tool earns its place, and the count is appropriate—neither too sparse nor excessive.

    Completeness5/5

    The tool surface covers the full expected workflow: understanding the backend's capabilities, selecting a case, and performing the analysis (which includes retrieval and citations). No additional operations seem necessary for the apparent read-only analysis domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources