Skip to main content
Glama
hvj78

MEK-MCP

by hvj78

mek_browse_index

Browse the controlled-vocabulary index of a catalogue field to locate exact term forms before running advanced searches.

Instructions

Browse the controlled-vocabulary index of a catalogue field around a given term. Use this BEFORE subject/type/name searches to discover the exact term forms stored in the catalogue, then run mek_advanced_search with the returned search_value strings.

Returns: {field, term, entries: [{display, search_value}]}. Pass search_value (not display) as the value in mek_advanced_search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesTerm to position the index at; the browser returns the vocabulary entries around/containing it (e.g. 'néprajz' lists 'magyar néprajz', 'tárgyi néprajz', 'vallási néprajz', ...).
fieldYesField whose controlled-vocabulary index to browse. One of: author, author_role, collection_title, contributor, contributor_role, corporate_author, creative_commons, document_type, format, geographic_subject, language, main_title, original_language, original_title, parallel_title, part_title, period_subject, printed_source, publisher, rights_note, rights_owner, series, subject, subtitle. Most useful: subject, geographic_subject, document_type, author, language.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations, but description discloses return structure and the distinction between display and search_value. Could mention error behavior if term not found, but overall transparent for a read-only browse.

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?

Two concise sentences plus return summary; purpose and usage are front-loaded, no redundancy.

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 output schema exists, description covers purpose, parameter guidance, usage context, and how to chain with sibling, making it fully adequate for an agent.

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

Parameters5/5

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

Adds meaning beyond schema: explains term as a positioning point (not filter), lists most useful fields, and emphasizes using search_value (not display) downstream.

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?

Clearly states 'Browse the controlled-vocabulary index of a catalogue field around a given term', distinguishing it from search tools like mek_advanced_search.

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 instructs 'Use this BEFORE subject/type/name searches' and directs to pass search_value to mek_advanced_search, providing clear when-to-use and chaining guidance.

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