Skip to main content
Glama
telota

bbaw-dse-mcp

by telota

cs_search_for_gnd_id

Find GND IDs for persons, places, and corporate bodies by name, and use them for correspSearch filtering and metadata enrichment.

Instructions

Search for GND IDs by name using Lobid GND API.

PURPOSE: Find GND identifiers for persons, places, or corporate bodies.

WHEN TO USE:

  • When you need a GND ID for correspSearch filtering

  • To resolve person names to standard identifiers

  • For enriching metadata with authority data

WHEN NOT TO USE:

  • For full entity data → use get_gnd_entity() tools

  • For non-GND authority data → use other services

Args: name_query: Name or term to search for (e.g., "Goethe", "Humboldt") limit: Maximum number of results to return

Returns: List of dicts with 'id' (GND URI) and 'label' for matching entities

Example: >>> results = await search_for_gnd_id("Wilhelm von Humboldt") >>> gnd_id = results[0]['id'].split('/')[-1] # Extract ID from URI >>> letters = await search_correspondences(person_gnd=gnd_id)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
name_queryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It transparently states the use of the Lobid GND API, describes the return format as a list of dicts with 'id' and 'label', and includes an example showing how to extract the GND ID from the URI. It does not mention error handling or rate limits, but for a simple search tool the key behaviors are adequately disclosed.

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 well-structured with clear section headings (PURPOSE, WHEN TO USE, WHEN NOT TO USE, Args, Returns, Example). Each section is concise and purposeful, and the example adds practical value without redundancy, making it easy for an agent to parse.

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 the lack of annotations and minimal schema, the description is remarkably complete. It covers purpose, usage, parameters, return values, and includes a detailed usage example with async syntax, showing the output and subsequent use. This provides all necessary context for an agent to select and invoke the tool correctly.

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?

Schema description coverage is 0%, and the description fully compensates by documenting both parameters in the Args section: name_query is described as 'Name or term to search for' with examples like 'Goethe', and limit is defined as 'Maximum number of results to return'. This adds meaningful semantics far beyond the bare schema types.

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 'Search for GND IDs by name using Lobid GND API' and further defines the PURPOSE as finding GND identifiers for persons, places, or corporate bodies. This distinguishes it from sibling tools like cs_search_for_geonames_id and cs_search_wikidata_entity, which target different ID systems.

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?

The description includes explicit WHEN TO USE sections, stating to use this tool when needing a GND ID for correspSearch filtering, resolving person names, or enriching metadata with authority data. It also provides WHEN NOT TO USE guidance, directing users to get_gnd_entity() for full entity data and other services for non-GND authority data, thereby clarifying alternatives.

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/telota/bbaw-dse-mcp'

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