Skip to main content
Glama

Dblp

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Authors

search_authors
Read-onlyIdempotent

Search DBLP authors by name. Returns canonical id, affiliation, ORCID when available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hitsNo1-1000 (default 30)
firstNo0-based offset
queryYesAuthor name (full or partial)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "Geoffrey Hinton"
+  },
+  {
+    "hits": 100,
+    "query": "Bengio"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "properties": {
+        "completed": {
+          "description": "Completion timestamp",
+          "type": "number"
+        },
+        "hit": {
+          "description": "Array of author results",
+          "items": {
+            "properties": {
+              "affiliation": {
+                "description": "Author affiliation if available",
+                "type": "string"
+              },
+              "info": {
+                "description": "Author info string",
+                "type": "string"
+              },
+              "name": {
+                "description": "Canonical author name",
+                "type": "string"
+              },
+              "orcid": {
+                "description": "ORCID identifier if available",
+                "type": "string"
+              },
+              "url": {
+                "description": "DBLP author page URL",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "hits": {
+          "description": "Total number of author results",
+          "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"
+}
  2. First observed

TDQS

A4/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, setting a safe read-only expectation. The description adds value by specifying the return fields (canonical id, affiliation, ORCID) and the data source (DBLP), which are behavioral details beyond the annotation hints.

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 a single sentence that efficiently states purpose and return information. No unnecessary words; it is front-loaded with the action and resource. Every part earns its place.

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 low complexity (3 parameters, simple search), the description covers the core purpose and return fields. An output schema exists, so details on structure are not required. However, pagination behavior (first parameter) is not mentioned, but the schema covers it. Overall adequate for the tool's simplicity.

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

Parameters3/5

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

Schema description coverage is 100%, with all three parameters (query, hits, first) already described. The description only adds 'by name' which aligns with the query parameter; it does not elaborate on format or usage beyond the schema. Thus, minimal added value, meeting the baseline for high coverage.

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 the verb 'Search', the resource 'DBLP authors', and specifies what it returns ('canonical id, affiliation, ORCID'). This distinguishes it from siblings like 'search_publications' and 'search_venues', which target different resources.

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 use for author name search but does not explicitly state when to choose this tool over alternatives like 'search_publications' or 'search_venues'. No exclusion criteria or when-not-to-use guidance is provided, which is a gap given the presence of similar sibling tools.

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

All Dblp toolsInspect
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.

Resources