Skip to main content
Glama

submit_meta_review

Prepare and preview a meta-review summarizing reviews and providing a recommendation for conference paper submissions.

Instructions

Prepare a meta-review for submission. Returns a preview — call confirm_submission to post it.

Args: venue_id: The venue identifier. submission_number: The paper number. recommendation: Your recommendation (e.g., 'Accept', 'Reject', 'Accept (Poster)', etc.). metareview_text: The meta-review text summarizing reviews and your assessment. confidence: Your confidence level (scale depends on venue).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
venue_idYes
submission_numberYes
recommendationYes
metareview_textYes
confidenceYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The `submit_meta_review` tool implementation, which validates the user's role and stages a meta-review submission in the `pending_store`.
    @mcp.tool()
    async def submit_meta_review(
        venue_id: str,
        submission_number: int,
        recommendation: str,
        metareview_text: str,
        confidence: int,
    ) -> str:
        """Prepare a meta-review for submission. Returns a preview — call confirm_submission to post it.
    
        Args:
            venue_id: The venue identifier.
            submission_number: The paper number.
            recommendation: Your recommendation (e.g., 'Accept', 'Reject', 'Accept (Poster)', etc.).
            metareview_text: The meta-review text summarizing reviews and your assessment.
            confidence: Your confidence level (scale depends on venue).
        """
        client = get_client()
        profile_id = client.profile.id
    
        ac_groups = client.get_groups(
            prefix=f"{venue_id}/Submission{submission_number}/Area_Chair_",
            signatory=profile_id,
        )
        if not ac_groups:
            return f"Could not find your anonymous AC group for Submission #{submission_number}. Are you assigned as an Area Chair?"
    
        ac_anon_id = ac_groups[0].id
        content = {
            "metareview": {"value": metareview_text},
            "recommendation": {"value": recommendation},
            "confidence": {"value": confidence},
        }
        payload = {
            "invitation": f"{venue_id}/Submission{submission_number}/-/Meta_Review",
            "signatures": [ac_anon_id],
            "content": content,
        }
        preview = "\n".join([
            f"## Meta-Review Preview for Submission #{submission_number}",
            f"**Signing as:** {ac_anon_id}",
            f"**Recommendation:** {recommendation}",
            f"**Confidence:** {confidence}",
            f"\n{metareview_text}",
        ])
        confirmation_id = pending_store.add(action="submit_meta_review", payload=payload, preview=preview)
        return f"{preview}\n\n---\n**Confirmation ID:** `{confirmation_id}`\n\nCall `confirm_submission` with this ID to post the meta-review."
Behavior4/5

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

With no annotations provided, the description carries the full burden and successfully discloses that this returns a preview rather than completing the submission. However, it does not explicitly clarify whether calling this creates a persistent draft in the system or what side effects occur beyond returning the preview.

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?

Front-loaded with purpose and workflow in the first two sentences, followed by a structured Args block. No redundant text; every sentence serves either functional description or parameter documentation. Appropriate length for the complexity.

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?

Fully complete for a 5-parameter tool with output schema: it documents all parameters (compensating for schema gaps), explains the return behavior (preview), references the necessary follow-up tool (confirm_submission), and requires no additional context for correct invocation.

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?

Given 0% schema description coverage, the Args section comprehensively compensates by documenting all 5 required parameters, including specific examples for 'recommendation' ('Accept', 'Reject', etc.) and noting that confidence 'scale depends on venue'—adding critical semantic context absent from the schema.

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?

The description uses specific verb 'Prepare' with resource 'meta-review' and explicitly distinguishes from sibling 'confirm_submission' by stating it only returns a preview, while also differentiating from 'submit_review' via the 'meta-review' terminology.

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?

Explicitly states the two-step workflow: 'Returns a preview — call confirm_submission to post it.' This provides clear guidance on when to use this tool (preparation) versus the sibling tool (finalization), effectively acting as when/when-not guidance.

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