Skip to main content
Glama
lacausecrypto

io.github.lacausecrypto/poetrydb

by lacausecrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to io.github.lacausecrypto/poetrydb

No user-submitted related servers found.

    Related Servers

    • mcp-poetry

      pipeworx-io
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables searching and retrieving poems from the PoetryDB API by title, keyword, or author, and also provides random poems for inspiration.
      5 npm
      MIT

    • io.github.FreyaBit/shanghai

      FreyaBit
      A
      license
      B
      quality
      B
      maintenance
      Exposes 97 official Shanghai Library open data APIs and the Sou-Yun poetry database (1.99 million poems) as 12 MCP tools, covering genealogy, ancient books, calligraphy, historical buildings, and more. Enables MCP clients to query these datasets using natural language.
      12
      4
      MIT

    • yellow-pages

      ethank64
      F
      license
      A
      quality
      D
      maintenance
      Exposes two MCP tools (discover and execute) that enable agents to query an OpenAPI schema via natural language and execute matched API operations.
      2
      -

    • mcphello-mcp-server

      goldct
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides access to a curated database of over 1,500 MCP tools with quality scores. Enables searching, browsing trending tools by category, discovering random tools, and retrieving detailed information about specific MCP tools.
      -
    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

    B3.4/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but get_sonnets and get_haikus overlap with search_by_linecount since 14-line and 3-line poems are special cases. An agent might be unsure whether to use the specialized get_* tools or the more general search_by_linecount.

    Naming Consistency3/5

    Tool naming mixes several patterns: catalog_* (catalog_overview, catalog_category), search_by_* (search_by_author, search_by_title, etc.), list_* (list_authors, list_titles), get_* (get_sonnets, get_haikus), and random_poem (no prefix). This inconsistency can make tool selection less predictable.

    Tool Count5/5

    With 12 tools, the count is well within the expected range for a domain-specific server. Each tool serves a distinct function and none feels superfluous or excessive for a poetry database.

    Completeness4/5

    The toolset covers searching, listing, and random access, along with helpful meta-tools for discovery. Minor gaps include the lack of a direct 'get poem by ID' or 'get full poem content' endpoint, which forces reliance on search results. Overall, the surface is reasonably complete for common poetry browsing workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources