Skip to main content
Glama

Get Venue

get_venue_context
Read-onlyIdempotent

Retrieve a conference or journal’s top authors, research directions, and yearly activity using a venue key or /venue/ URL. Use it to answer questions about venue focus and prolific authors.

Instructions

Describe a conference or journal: its top authors and directions, by year.

Use for "what did NeurIPS 2025 focus on" or "who publishes most at X".

Venue keys are opaque hashes (e.g. "d7bf22905bd6"), never human-readable names like "icml". Find the key first via search_lacuna(search_type="venue") or pass a /venue/... page URL.

view selects the response shape:

  • "context" (default, recommended): compact venue context — capped top authors, non-placeholder top clusters, and a recent-activity slice (the requested year is always included), with the duplicated venue block and full year histogram dropped server-side.

  • "full": the complete venue context (full year histogram, all top authors/ clusters, duplicated venue record).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "venue_key_or_url": "<venue_key_or_url>"
    },
    "name": "get_venue_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNocontext
yearNo
venue_key_or_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds the non-obvious constraint that venue keys are opaque hashes and never human-readable names — a failure mode that would otherwise cause wrong calls. It further discloses that view="context" drops the duplicated venue block and full year histogram server-side, which tells the agent what data is intentionally absent from the response.

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?

Front-loaded purpose, then usage examples, then the key-format caveat, then a bulleted view breakdown — an agent can stop reading early and still call correctly. Slight redundancy in restating the duplicated venue block/histogram dropping in both bullets keeps it from a 5.

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

Completeness5/5

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

An output schema exists, so return values need no explanation, and the description still characterizes the two response shapes. For a three-parameter read tool with opaque keys, the definition covers everything needed to call it correctly on the first try.

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

Parameters5/5

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

With 0% schema description coverage, the description carries the full burden and does so for all three parameters: venue_key_or_url (hash format or /venue/ page URL), view (explicit semantics of both enum values and the default), and year (guaranteed to be included in the recent-activity slice). This is meaning well beyond what the bare schema conveys.

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 ("Describe a conference or journal: its top authors and directions, by year") and scopes it with concrete example questions. An agent can tell this apart from the author/institution siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit example phrasings for when to use it, and critically states the prerequisite workflow: resolve the opaque key first via search_lacuna(search_type="venue") or pass a /venue/... URL. It also documents when to pick each view, with a stated default and recommendation.

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