Skip to main content
Glama
Sign In
APEX Everything MCP Server

APEX Everything MCP Server

by GlacierEQ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

llm_groq

Send prompts to Groq LLM to generate AI text responses. Specify model and token limits for controlled output.

Instructions

Send prompt to groq LLM

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": {
      "prompt": "<prompt>"
    },
    "name": "llm_groq"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptYes
modelNo
max_tokensNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only states the action without mentioning side effects (e.g., cost, API key requirements, or response format).

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

Conciseness3/5

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

The description is a single, front-loaded sentence, which is concise. However, it is too brief for the tool's complexity (3 params, no schema descriptions), lacking necessary details.

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

Completeness2/5

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

Despite having 3 parameters, no output schema, no schema descriptions, and no annotations, the description only provides a minimal purpose. It fails to cover parameter semantics, usage context, or return value.

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

Parameters2/5

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

Schema description coverage is 0% for 3 parameters. The description only implies the 'prompt' parameter via the word 'prompt' but fails to explain 'model' or 'max_tokens', adding little value beyond the schema.

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

Purpose4/5

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

The description 'Send prompt to groq LLM' clearly identifies the verb (send) and resource (groq LLM), and distinguishes it from sibling tools like llm_anthropic or llm_openai by naming the specific provider.

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?

The description provides no guidance on when to use this tool over alternatives from the sibling list (e.g., llm_openai, llm_gemini). An agent must infer usage solely from the tool name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools