rumors-lines-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port to use when running the Streamable HTTP transport. Change via the PORT environment variable. | 8080 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_collectionsA | List published pick-up line collections: URL, title, language (BCP-47) and line count. |
| get_linesA | Get lines from one collection by its URL. Each line comes with a literal English gloss. |
| random_lineB | One random line, optionally narrowed by language and register. |
| search_linesB | Case-insensitive substring search across native text, transliteration and English gloss. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct action: list_collections enumerates collections, get_lines retrieves lines for a given collection URL, random_line returns a single random line with optional filters, and search_lines performs substring search. The overlap between get_lines and search_lines is minimal because get_lines requires a collection URL while search_lines searches across all lines; an agent can easily choose.
All names use snake_case and are readable, but random_line breaks the verb_noun pattern used by list_collections, get_lines, and search_lines by using an adjective instead of a verb. This is a minor deviation from an otherwise consistent convention.
Four tools are well-scoped for a read-only pick-up line browsing service: discover collections, fetch lines, get a random line, and search. No tool feels redundant or missing for the core purpose.
The read-only surface covers listing, fetching, random sampling, and text search, which are the primary workflows. Minor gaps include no pagination for large collections or search results and no explicit way to discover available languages/registers beyond collection language metadata, but agents can work around these.