Skip to main content
Glama
hvj78

MEK-MCP

by hvj78

mek_simple_search

Search the Hungarian Electronic Library by title, author, subject, or ID with automatic accent-insensitive matching.

Instructions

Simple search in the MEK catalogue by title, subject, author and/or MEK ID. All given words are combined with AND. Words may be typed in lowercase and without accents: if nothing is found, the MEK server automatically retries accent-free and then stemmed.

Good for quick, broad lookups. For field-precise queries, OR-logic, exclusions (NOT) or language/type filtering use mek_advanced_search.

Returns: {total, offset, limit, hits: [{mek_id, url, authors, title, date_added}], has_more}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax hits per page. Server supports 10, 50 or 100; the value is rounded up to the nearest supported size.
titleNoWords from the title (main/sub/series title). All words must occur (AND). Truncation with *, accents optional. Empty = not filtered.
authorNoAuthor / editor / translator name words, e.g. 'Petőfi Sándor' or 'Orwell'.
mek_idNoNumeric MEK identifier of a specific document, e.g. '9439'.
offsetNoResult offset for paging (0-based, in items).
subjectNoWords from the topic: subject headings, sub-collection or document type, in Hungarian (e.g. 'néprajz', 'történelem', 'regény').

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, but description fully discloses behavioral traits: AND combination of words, retrying with accent-free and stemmed versions, rounding of limit to supported sizes, and the return format.

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?

Concise and well-structured: first sentence states purpose, then details on usage, alternatives, and return format. No unnecessary information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 6 parameters with full schema, an output schema, and no required params, the description covers all necessary context including behavioral details and alternatives, making it complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, baseline 3, but description adds value by explaining AND logic for title, example for author, Hungarian context for subject, and limit rounding behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it performs a simple search by title, subject, author, and/or MEK ID, and explicitly distinguishes from mek_advanced_search by noting it's for quick, broad lookups.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use (quick, broad lookups) and when not to (field-precise queries, OR-logic, exclusions, language/type filtering) and names the alternative tool mek_advanced_search.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hvj78/MEK-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server