Skip to main content
Glama

Search Venues

search_venues
Read-onlyIdempotent

Search the conferences and journals that appear in the dblp bibliography, from a stored copy of the publisher's CC0 bulk release. Returns each venue name as dblp writes it, how many records name it and the year span. Most-used first. 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": "ICLR"
    },
    "name": "search_venues"
  }
}

Input Schema

NameRequiredDescriptionDefault
hitsNo1-100 (default 30)
firstNo0-based offset
queryYesVenue name or acronym, e.g. "ICLR" or "Nature"

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": {
      +      "first_year": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "last_year": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "records": {
      +        "description": "Records indexed under the venue",
      +        "type": "number"
      +      },
      +      "venue": {
      +        "type": "string"
      +      }
      +    },
      +    "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 venue results",
      -      "items": {
      -        "properties": {
      -          "acronym": {
      -            "description": "Venue acronym if available",
      -            "type": "string"
      -          },
      -          "info": {
      -            "description": "Venue info string",
      -            "type": "string"
      -          },
      -          "name": {
      -            "description": "Venue full name",
      -            "type": "string"
      -          },
      -          "url": {
      -            "description": "DBLP venue page URL",
      -            "type": "string"
      -          }
      -        },
      -        "type": "object"
      -      },
      -      "type": "array"
      -    },
      -    "hits": {
      -      "description": "Total number of venue 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: -"Venue name or acronym (e.g. \"ICLR\", \"Nature\")"New value: +"Venue name or acronym, e.g. \"ICLR\" or \"Nature\""
  3. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "query": "ICLR"
      +  },
      +  {
      +    "hits": 50,
      +    "query": "Nature Machine Intelligence"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "result": {
      +      "properties": {
      +        "completed": {
      +          "description": "Completion timestamp",
      +          "type": "number"
      +        },
      +        "hit": {
      +          "description": "Array of venue results",
      +          "items": {
      +            "properties": {
      +              "acronym": {
      +                "description": "Venue acronym if available",
      +                "type": "string"
      +              },
      +              "info": {
      +                "description": "Venue info string",
      +                "type": "string"
      +              },
      +              "name": {
      +                "description": "Venue full name",
      +                "type": "string"
      +              },
      +              "url": {
      +                "description": "DBLP venue page URL",
      +                "type": "string"
      +              }
      +            },
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "hits": {
      +          "description": "Total number of venue 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"
      +}
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With readOnlyHint and idempotentHint already supplied, the description still adds meaningful context: it reveals the data source is a stored copy of the bulk release, states that answers carry data_as_of, answered_from and the licence, and that results are returned most-used first. These disclosures about provenance and freshness go beyond the annotations. It falls short of a 5 only because it does not say how stale that stored copy is or how the licence field is formatted.

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?

Three sentences: the first defines the resource and its source, the second defines the return shape, the third covers provenance metadata. The scope and source are front-loaded, and no sentence is redundant.

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?

For a three-parameter read-only search with an output schema, the description covers data source, returned fields, ordering, and provenance fields, so an agent has everything needed to call it. The one gap is that it never states the matching behavior for the query string (exact acronym vs substring), which matters for a venue lookup.

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 descriptions already cover all three parameters at 100% coverage, including '1-100 (default 30)' for hits and '0-based offset' for first, so the baseline is 3. The description contributes only the ordering note ('Most-used first'), which clarifies what ordering the hits/first window reflects, but adds no query syntax or matching rules for the query parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Search' is paired with a precisely scoped resource: conferences and journals in the dblp bibliography, drawing on a stored copy of the CC0 bulk release. It could be confused with the sibling dblp_search_publications, but calling out 'venue name' and 'how many records name it' makes the returned entity type unambiguous. It stops short of a 5 because there is no explicit contrast with sibling tools.

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 tool clearly suits finding a venue's canonical dblp spelling, and the ranking is disclosed. But it never indicates when to use this rather than dblp_search_publications or dblp_search_authors, and it gives no exclusion such as 'does not return individual papers'. An agent must infer the boundary between the venue and publication tools.

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.