Reviewmetric
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REVIEWMETRIC_API_KEY | Yes | Your API key from the web dashboard |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| submit_manuscriptB | Submits a locally saved .docx manuscript to the ReviewMetric 15-agent AI pipeline. Args: file_path: The absolute path on the local computer to the .docx file. |
| check_analysis_statusA | Checks the status or retrieves the final report of a ReviewMetric analysis. Args: run_id: The unique UUID of the analysis run. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
Only two tools with clearly distinct purposes: one is for submission, the other for checking status. No overlap or ambiguity.
Both tool names follow a consistent verb_noun pattern in snake_case (submit_manuscript, check_analysis_status), with clear and descriptive names.
With only two tools for a described 15-agent AI pipeline, the tool count feels too thin for the apparent scope, lacking intermediate or management tools.
The tool surface is severely limited, covering only submission and status checking. Missing are operations such as listing runs, retrieving full reports, or managing analyses.