Skip to main content
Glama

Dblp Search Authors

dblp_search_authors
Read-onlyIdempotent

Search dblp authors by name from a stored copy of the publisher's CC0 bulk release. Returns the dblp person id, name variants, affiliations, ORCID when listed, and publication count; the most-published people come first, which separates the famous namesake from the rest. Every answer carries data_as_of, answered_from and the licence.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "Geoffrey Hinton"
    },
    "name": "dblp_search_authors"
  }
}

Input Schema

NameRequiredDescriptionDefault
hitsNo1-100 (default 30)
firstNo0-based offset
queryYesAuthor name, full or partial, e.g. "Yoshua Bengio" or "Hinton"

Output Schema

NameRequiredDescriptionDefault
hitsNo
countNoHits in this response
firstNo0-based offset of the first hit
queryNo
totalNoTotal matches; null when not counted
sourceNo
licenceNo
messageNoPresent on a zero-hit answer
data_as_ofNoDate of the dblp release the stored copy was built from
answered_fromNoWhere the answer came from (stored copy)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • addedOutput schema / properties / answered_from
      Added value: +{
      +  "description": "Where the answer came from (stored copy)",
      +  "type": "string"
      +}
    • addedOutput schema / properties / count
      Added value: +{
      +  "description": "Hits in this response",
      +  "type": "number"
      +}
    • addedOutput schema / properties / data_as_of
      Added value: +{
      +  "description": "Date of the dblp release the stored copy was built from",
      +  "type": "string"
      +}
    • addedOutput schema / properties / first
      Added value: +{
      +  "description": "0-based offset of the first hit",
      +  "type": "number"
      +}
    • addedOutput schema / properties / hits
      Added value: +{
      +  "items": {
      +    "properties": {
      +      "affiliations": {
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "aliases": {
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "name": {
      +        "type": "string"
      +      },
      +      "orcid": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "pid": {
      +        "description": "dblp person id",
      +        "type": "string"
      +      },
      +      "publications": {
      +        "type": "number"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / licence
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / message
      Added value: +{
      +  "description": "Present on a zero-hit answer",
      +  "type": "string"
      +}
    • addedOutput schema / properties / query
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / result
      Removed value: -{
      -  "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"
      -}
    • addedOutput schema / properties / source
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / total
      Added value: +{
      +  "description": "Total matches; null when not counted",
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / hits / description
      Previous value: -"1-1000 (default 30)"New value: +"1-100 (default 30)"
    • changedInput schema / properties / query / description
      Previous value: -"Author name (full or partial)"New value: +"Author name, full or partial, e.g. \"Yoshua Bengio\" or \"Hinton\""
  3. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real context beyond that: results come from a stored bulk snapshot (implying possible staleness), ordering is by publication count, and every response carries data_as_of and licence metadata.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence that front-loads the verb, resource and source, followed by return fields and a provenance note. Nothing is wasted, though the semicolon-chained clauses make it slightly crammed for one sentence.

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?

An output schema exists and annotations cover safety, so the description only needs to add provenance and ordering context — which it does, including the freshness caveat via data_as_of. Complete for the tool's complexity, with only explicit sibling routing absent.

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 coverage is 100%, so query, hits and first are already documented in the schema. The description's ranking statement is indirectly relevant to hits/first (the top-N are the most-published), but it adds no syntax or format guidance for the parameters themselves, so the baseline 3 applies.

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?

States a specific verb and resource ("Search dblp authors by name") plus the data source (a stored copy of the publisher's CC0 bulk release), and the returned identity fields make its role distinct from publication search. An agent can tell this resolves people, not papers, without opening the schema.

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?

Usage is implied rather than stated: the note that ranking "separates the famous namesake from the rest" hints at author-disambiguation use, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g. dblp_search_publications for works).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.