Dblp

Search Publications

search_publications

Read-onlyIdempotent

Search DBLP publications. Match by title / author / year / venue. Default page size 30, max 1000.

Input Schema

TableJSON Schema

Name	Required	Description
`hits`	No	Results per page, 1-1000 (default 30)
`first`	No	0-based offset (default 0)
`query`	Yes	Search term — title / author / DOI / venue

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "query": "deep learning neural networks"
+  },
+  {
+    "first": 0,
+    "hits": 50,
+    "query": "Yann LeCun"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "properties": {
+        "completed": {
+          "description": "Completion timestamp",
+          "type": "number"
+        },
+        "hit": {
+          "description": "Array of publication results",
+          "items": {
+            "properties": {
+              "authors": {
+                "description": "Author information",
+                "properties": {
+                  "author": {
+                    "description": "Author(s) name(s)",
+                    "type": [
+                      "array",
+                      "object"
+                    ]
+                  }
+                },
+                "type": "object"
+              },
+              "doi": {
+                "description": "DOI identifier",
+                "type": "string"
+              },
+              "ee": {
+                "description": "Electronic edition URL",
+                "type": "string"
+              },
+              "info": {
+                "description": "Publication info string",
+                "type": "string"
+              },
+              "title": {
+                "description": "Publication title",
+                "type": "string"
+              },
+              "type": {
+                "description": "Publication type (e.g., article, inproceedings)",
+                "type": "string"
+              },
+              "url": {
+                "description": "DBLP URL for the publication",
+                "type": "string"
+              },
+              "venue": {
+                "description": "Conference or journal name",
+                "type": "string"
+              },
+              "year": {
+                "description": "Publication year",
+                "type": "number"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "hits": {
+          "description": "Total number of results matching the query",
+          "type": "number"
+        },
+        "published": {
+          "description": "Number of results in this response",
+          "type": "number"
+        },
+        "start": {
+          "description": "0-based offset of first result",
+          "type": "number"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description adds value by specifying default page size (30) and maximum (1000), which are useful behavioral constraints.

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 sentences, front-loaded with key action and resource, no wasted words. Every sentence adds value.

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

Completeness4/5

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

Given the presence of an output schema and annotations, the description adequately covers pagination and match fields. It omits sorting or result handling, but is sufficient for a simple search tool.

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 covers 100% of parameters with descriptions, but the description adds semantic context that query can match by title, author, year, venue, and specifies page size limits, complementing the schema.

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 DBLP publications' with specific match fields (title, author, year, venue), distinguishing it from sibling tools like search_authors and search_venues.

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 usage for searching publications but does not explicitly state when to use vs. alternatives, nor provide exclusion criteria. Context from sibling tools helps but is not stated.

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

All Dblp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.