Skip to main content
Glama

list_venues

Retrieve all OpenReview venues where you currently serve as Reviewer, Area Chair, or Senior Area Chair to manage conference workflows.

Instructions

List all OpenReview venues where you have an active role (Reviewer, Area Chair, or Senior Area Chair).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The `list_venues` function serves as the MCP tool handler for listing OpenReview venues where the authenticated user has roles. It is decorated with `@mcp.tool()`, which registers it as an MCP tool.
    @mcp.tool()
    async def list_venues() -> str:
        """List all OpenReview venues where you have an active role (Reviewer, Area Chair, or Senior Area Chair)."""
        client = get_client()
        profile_id = client.profile.id
    
        groups = client.get_all_groups(member=profile_id)
    
        venues: dict[str, list[str]] = {}
        for group in groups:
            for suffix, role_name in ROLE_SUFFIXES.items():
                if group.id.endswith(suffix):
                    venue_id = group.id[: -len(suffix)]
                    if re.search(r"/Submission\d+", venue_id):
                        continue
                    if venue_id not in venues:
                        venues[venue_id] = []
                    venues[venue_id].append(role_name)
    
        if not venues:
            return "No active venue roles found for your account."
    
        lines = []
        for venue_id, roles in sorted(venues.items()):
            lines.append(f"- **{venue_id}** — {', '.join(roles)}")
        return "Your active venues:\n\n" + "\n".join(lines)
Behavior3/5

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

With no annotations provided, the description carries the full burden. It successfully discloses the filtering behavior (active roles only, specific role types) but omits other behavioral traits like error handling when no roles exist, what constitutes 'active', or rate limiting. Output schema exists, reducing the burden for return value documentation.

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?

Single, dense sentence with zero waste. Front-loaded with action verb, immediately followed by resource and qualifying scope. Parenthetical enumeration of roles provides precise context without verbosity.

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 zero parameters and existence of output schema, the description appropriately focuses on semantic scope (active roles only). Sufficient for this low-complexity tool, though could be strengthened by noting this is typically the entry point for venue-specific operations.

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

Parameters4/5

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

Input schema has 0 parameters, establishing a baseline of 4 per scoring rules. The description adds no parameter-specific information (as there are none), but implicitly constrains the output behavior rather than input semantics.

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?

Excellent specific verb 'List' with clear resource 'OpenReview venues' and precise scope constraint 'where you have an active role'. Enumerates specific roles (Reviewer, Area Chair, Senior Area Chair) which distinguishes this from generic venue lists and clarifies its relationship to sibling tools that operate on submissions/reviews within those venues.

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

Usage Guidelines4/5

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

Implicitly guides usage by specifying which roles qualify (Reviewer, Area Chair, Senior Area Chair), helping the agent understand when results will be returned. However, lacks explicit guidance on sequencing (e.g., 'Use this first to get venue IDs before using list_assignments') or exclusions (archived vs active venues).

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/michaelqshieh/openreview-mcp'

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