Skip to main content
Glama

Search CS Papers

dblp.cs.search
Read-onlyIdempotent

Search over 7 million computer science publications from DBLP by title, keyword, or topic. Get results with authors, venue, year, and DOI for papers from conferences like NeurIPS, ICML, CVPR, ACL.

Instructions

Search 7M+ computer science publications on DBLP by title, keyword, or topic. Returns title, authors, venue (NeurIPS, ICML, CVPR, ACL, etc.), year, DOI. The largest CS-specific bibliography — covers journals, conferences, and workshops (DBLP, CC0)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query — paper title, keyword, or topic (e.g. "transformer attention", "graph neural network", "LLM reasoning")
yearNoFilter by publication year (e.g. 2024)
limitNoNumber of results (1-50, default 20)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
Behavior4/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. Description adds context about the size of the database, venue examples, and data source (DBLP, CC0), which goes beyond annotations but does not disclose pagination or rate limits.

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?

Description is two concise sentences. First sentence states functionality and return fields. Second sentence adds context about the database. No redundancy or unnecessary words.

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 output schema exists, description adequately covers scope and output fields. Could mention pagination but not required for a straightforward search tool. Missing details about error messages or result ordering, but still sufficiently complete.

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?

Input schema covers all parameters with descriptions (100% coverage). Description does not add additional semantics beyond what is already in the schema, so baseline 3 is appropriate.

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?

Description clearly states the verb 'search' and resource 'CS publications on DBLP' with specific details about scope (7M+, titles, authors, venue, year, DOI). Distinguishes from sibling 'dblp.cs.author' by focusing on papers rather than authors.

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?

Description implies usage for finding papers by title/keyword/topic but does not explicitly state when to use this tool over alternatives like dblp.cs.author. No when-not-to-use or exclusion criteria provided.

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/whiteknightonhorse/APIbase'

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