Skip to main content
Glama
convergeqa

convergeqa-mcp

Official
by convergeqa

convergeqa_critique_start

Start a private authenticated Critique agent review to get a multi-model analysis of your content.

Instructions

Start a private authenticated Critique agent review.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelsYes
promptNoSynthetic or user-approved text to review. Not returned.
base_urlNoConvergeQA base URL.https://convergeqa.net
templateNoGeneral
model_tierYesRequired for agent review starts.
api_key_envNoUppercase environment variable name containing a ConvergeQA Developer API key.CONVERGEQA_API_KEY
prompt_fileNoLocal file path containing text to review. Not returned.
extra_promptNo
document_nameNoAgent Review
max_spend_usdNoOptional advisory spend cap for this service-account request.
system_promptNo
credential_kindNoauto
idempotency_keyNo
synthesis_modelNo
reference_materialNo
redact_private_urlsNo
additional_instructionsNo
service_account_key_envNoUppercase environment variable name containing the ConvergeQA service-account key.CONVERGEQA_SERVICE_ACCOUNT_KEY
Behavior2/5

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

No annotations are provided, so the description must carry the burden. It mentions 'private authenticated' but does not explain authentication requirements, whether the operation is read-only or destructive, or any other behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single vague sentence; it is under-specified rather than concise.

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

Completeness1/5

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

Given 18 parameters, no output schema, and no annotations, the description is severely incomplete, lacking information on what the tool returns or how to use it.

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

Parameters1/5

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

The description adds no meaning beyond the input schema, and with schema description coverage at only 39%, it fails to compensate for undocumented parameters.

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

Purpose3/5

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

The description states a specific verb ('Start') and resource ('Critique agent review'), but it is vague about what a 'Critique agent review' entails and does not distinguish this tool from siblings like 'convergeqa_iterate_start' or other critique tools.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives, nor any conditions or exclusions for its use.

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/convergeqa/convergeqa-mcp'

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