Skip to main content
Glama

Get an independent review

submit_review_request

Independent review of AI-generated work in this conversation: your answer, or code, a pull request, a plan, an analysis or a draft produced with AI. Covers requests such as: is this right, a hallucination check, a fact-check, what's missing, challenge my assumptions, an adversarial review, a gate review, or an independent sign-off before merging, shipping or submitting. A panel of reviewers running on another company's AI model returns a verdict, inaccuracies with corrections, gaps, follow-up questions and a scored report card.

The review covers the complete text submitted, so an unabridged copy of the work gives a complete result; a revised draft can be reviewed again.

Not for: verifying a single factual claim against sources, questions about an uploaded document, detecting whether text was AI-written, evaluating the user's own AI agents, writing or editing, or discussing a review that has already been returned ("Do you agree?", "Was that fair?").

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": {
      "reviewBrief": "<reviewBrief>"
    },
    "name": "submit_review_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
reviewBriefYesStructured review brief synthesized from conversation context
consultantIdNoReview type. Currently all reviews use an independent panel of analysts.
additionalContextNoAdditional context (e.g., {artifact: 'pull request', stakes: 'pre-merge gate'} or {domain: 'tax law', jurisdiction: 'Germany'})

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / reviewBrief / properties / constraints / description
      Previous value: -"Key facts, requirements, and constraints from the conversation"New value: +"Facts about the situation the work was written for, one per entry (e.g., 'written for one existing customer', 'the customer asked for stricter scores', 'targets Node 20 on Cloud Run')"
  2. Changed1 schema field changed
    • changedInput schema / properties / reviewBrief / properties / responseUnderReview / description
      Previous value: -"The AI-generated work under review (your answer, or the code, PR summary, plan, analysis or draft), as-is. Do not omit, summarize, or condense any content."New value: +"The complete, unabridged text of the AI-generated work under review (your answer, or the code, PR summary, plan, analysis or draft)."
  3. Changed4 schema fields changed
    • changedInput schema / properties / additionalContext / description
      Previous value: -"Additional context (e.g., {petType: 'Golden Retriever', petAge: '2 years'})"New value: +"Additional context (e.g., {artifact: 'pull request', stakes: 'pre-merge gate'} or {domain: 'tax law', jurisdiction: 'Germany'})"
    • changedInput schema / properties / reviewBrief / properties / objective / description
      Previous value: -"What the user is trying to achieve"New value: +"What the user is trying to achieve (e.g., 'merge PR #42 safely', 'submit this manuscript', 'decide whether to refinance')"
    • changedInput schema / properties / reviewBrief / properties / responseUnderReview / description
      Previous value: -"The specific AI response the user wants reviewed. Provide the response text as-is — do not omit, summarize, or condense any content."New value: +"The AI-generated work under review (your answer, or the code, PR summary, plan, analysis or draft), as-is. Do not omit, summarize, or condense any content."
    • changedInput schema / properties / reviewBrief / properties / userConcerns / description
      Previous value: -"User's specific concerns about the response"New value: +"What the user is worried about (e.g., 'the retry logic', 'whether the statistics section holds up')"
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The description adds meaningful behavioral context beyond the annotations: the review is performed by a panel running on another company's AI model, and the result includes a verdict, inaccuracies with corrections, gaps, follow-up questions, and a scored report card. It also explains that the complete submitted text is reviewed and that revised drafts can be reviewed again. It does not cover latency, cost, or detailed data-handling/privacy implications of sending work to an external model, which keeps it from a 5.

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?

The description is front-loaded with the core purpose and then organizes coverage examples, return contents, complete-text behavior, and exclusions into clear paragraphs. It is somewhat long, but most of the length is justified by the need to distinguish supported review requests from unsupported adjacent tasks. A few of the example lists are slightly repetitive, but there is no major wasted text.

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?

For a complex open-world, non-read-only review submission tool with a nested input schema and no output schema, the description provides enough context to call it correctly. It explains what the tool does, what it returns, how complete text affects the result, and which nearby tasks are out of scope. Combined with the fully described schema, no critical agent-facing gap remains.

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 description coverage is 100%, so the nested reviewBrief fields and their meanings are already well documented. The description reiterates that the complete unabridged text is what gets reviewed and that revised drafts can be resubmitted, but it does not add substantial semantics for objective, constraints, userConcerns, consultantId, or additionalContext beyond the schema. With the schema doing the heavy lifting, a 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?

The description states a specific action and resource: submitting AI-generated work in the conversation for independent review by a panel of reviewers. It clearly explains what the review covers and what it returns, including verdict, inaccuracies, gaps, follow-up questions, and a scored report card. The purpose is unambiguous even without sibling tools to compare against.

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?

Usage is explicitly defined with concrete examples such as hallucination checks, fact-checks, challenge-my-assumptions requests, adversarial reviews, gate reviews, and sign-off before merging or shipping. The description also includes a detailed 'Not for' section listing exclusions like verifying a single factual claim, uploaded-document questions, AI-text detection, evaluating the user's own agents, writing/editing, and discussing an already-returned review. This is exactly the when-to-use and when-not-to-use guidance an agent needs.

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.

Resources