MCP-DBLP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Search DBLP for publications using a boolean query string. Arguments:
|
| fuzzy_title_searchA | Search DBLP for publications with fuzzy title matching. Arguments:
|
| get_author_publicationsA | Retrieve publication details for a specific author with fuzzy matching. Arguments:
|
| get_venue_infoA | Retrieve detailed information about a publication venue. Arguments:
|
| calculate_statisticsA | Calculate statistics from a list of publication results. Arguments:
|
| export_bibtexA | Export BibTeX entries from a collection of HTML hyperlinks. Arguments:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| MCP-DBLP Instructions | Basic instructions for using the DBLP tools; get this prompt before any interaction with MCP-DBLP. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose with no ambiguity: calculate_statistics processes existing results, export_bibtex handles BibTeX export, fuzzy_title_search and search provide different search methods, get_author_publications focuses on authors, and get_venue_info targets venues. The tools cover different aspects of the DBLP domain without overlap.
All tool names follow a consistent verb_noun pattern with snake_case: calculate_statistics, export_bibtex, fuzzy_title_search, get_author_publications, get_venue_info, and search. The naming is predictable and readable throughout the set.
With 6 tools, the count is well-scoped for a DBLP server, covering key operations like search, author/venue info, statistics, and BibTeX export. Each tool earns its place without feeling thin or bloated, suitable for typical academic workflows.
The tool set provides strong coverage for core DBLP operations including search, author/venue retrieval, and data export, with minor gaps such as no direct tool for updating or deleting data (though this may be intentional for a read-heavy domain). Agents can effectively navigate publication workflows with these tools.