Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AQUA_MODELNoModel name to use when calling an external model via run_agent_with_external_model.
AQUA_API_KEYNoAPI key for an OpenAI-compatible endpoint, used only by the run_agent_with_external_model tool. Never pass in chat.
AQUA_BASE_URLNoBase URL for the OpenAI-compatible endpoint. Defaults to https://api.openai.com/v1 if not set.https://api.openai.com/v1

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
check_citation_integrityA

Flag verbatim word-runs of 3+ words shared between a draft passage and one or more source texts — a real paraphrase check, not AI-detection evasion.

list_supported_journalsA

List known journal formatting profiles (abstract word limit, keyword count, citation style, AI-disclosure requirement). Use this to ask the user which journal applies before drafting an abstract or AI-disclosure statement — never assume one journal's limits apply to another.

draft_ai_disclosureA

Produce the 'Declaration of generative AI use' statement text for the given tool name and reason it was used — IF the target journal is known to require one. Pass journal (a key from list_supported_journals) so this can check; without it, this returns a prompt to ask the user instead of guessing whether a disclosure is required or what it should say.

run_agent_with_external_modelA

Run one of the six manuscript-writing agents against an external OpenAI-compatible model, instead of the model your MCP client already uses.

The API key is never passed as an argument here — set it once as the AQUA_API_KEY environment variable in your MCP client's server config.

agent_name: one of "literature", "drafting", "results", "abstract", "copyedit", "integrity". journal: a key from list_supported_journals, for agents whose rules are journal-specific (abstract, drafting, integrity). Leave blank and the agent will ask the user which journal applies instead of guessing. model: overrides the AQUA_MODEL environment variable for this call. base_url: overrides the AQUA_BASE_URL environment variable for this call (defaults to https://api.openai.com/v1; point this at any OpenAI-compatible endpoint, e.g. a local Ollama/LM Studio server).

Prompts

Interactive templates invoked by user choice

NameDescription
literature-agentFind and vet real literature/citations for the manuscript.
drafting-agentDraft Introduction, Materials and Methods, or Discussion.
results-agentTurn supplied data/tables into Results-section prose.
abstract-agentDraft the Title, Abstract, and Keywords from a finished draft.
copyedit-agentSentence-level copyediting without changing claims or data.
integrity-agentCheck citation integrity and draft the AI-use disclosure.

Resources

Contextual data attached and managed by the client

NameDescription
human_only_rolesRACI roles that stay human-only no matter which AI model is used.
journal_profilesKnown journal formatting profiles (abstract limit, keyword count, citation style, AI-disclosure requirement) — only facts confirmed by reading that journal's own author guide.

TDQS

A4.3/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a distinct operation: checking citation integrity, listing journal profiles, drafting AI disclosures, and running writing agents. No two tools overlap in purpose; descriptions even cross-reference each other to prevent misselection (e.g., draft_ai_disclosure requires a journal key from list_supported_journals).

Naming Consistency4/5

All tool names use snake_case with a leading verb (check, list, draft, run) followed by a noun phrase. The pattern is consistent, though 'run_agent_with_external_model' is longer and embeds a qualifier, making it slightly less parallel than the others. Overall, naming is predictable.

Tool Count5/5

With 4 tools, the server is well-scoped for its niche purpose of supporting aquaculture manuscript writing. Each tool has a clear role, and none feels redundant or missing. The count is appropriate for a focused MCP server.

Completeness4/5

The tools cover the core workflow: checking citation integrity, retrieving journal requirements, generating AI disclosures, and running various writing agents. Minor gaps exist (e.g., no explicit tool to list agents, but run_agent_with_external_model includes the list in its description; no direct formatting tool, but agents likely handle it). Overall, the surface is reasonably complete for the stated domain.

Maintenance

ActivityMaintained
ResponsivenessNo issues