search_lines
Case-insensitive substring search across native text, transliteration and English gloss.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | ||
| limit | No | ||
| query | Yes |
Rumors pick-up lines
by app.rumors
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.3/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It does disclose meaningful behavior: case-insensitive substring matching across three specific text fields. However, it does not mention result ordering, pagination, empty-result behavior, or any access or rate-limit considerations, so there are clear gaps.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise, front-loaded sentence. Every word adds meaning: case-insensitive, substring, and the three searched fields. There is no redundancy or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple search tool, the description covers the core matching behavior, but with no annotations and no output schema it should also clarify the role of lang, mention that matching lines are returned, and ideally point to alternatives. It is adequate but not complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate, but it only adds meaning to the query parameter by indicating which fields are searched. It provides no extra semantics for the lang or limit parameters, which are left entirely to the schema's default/min/max clues.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('search'), a clear resource (lines), and the matching scope (native text, transliteration, English gloss). It distinguishes the tool from get_lines and random_line by describing a search behavior, though it does not explicitly contrast it with siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use the tool: when a case-insensitive substring search across those fields is needed. However, it gives no explicit guidance about when not to use it or which sibling alternative to prefer, leaving the usage context implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4/5.0
Disambiguation5/5
Each tool serves a distinct purpose: listing collections, retrieving all lines from a collection, getting a random line, and searching lines. No two tools appear to do the same thing, and the descriptions make the boundaries clear.
Naming Consistency4/5
Three tools follow a clear verb_noun pattern (get_lines, list_collections, search_lines), but random_line is an adjective_noun exception. Overall the naming is predictable and readable, with only a minor deviation.
Tool Count5/5
Four tools is well-scoped for a read-only pick-up line server. Each tool earns its place and there is no bloat or noticeable thinness.
Completeness5/5
The server covers the core read workflows: discover collections, fetch lines from a collection, get a random line, and search across all lines. There are no obvious missing operations for the stated domain.