Skip to main content
Glama
crowllm-mcp

crowllm-mcp

Official
by crowwdev

Chat through CrowLLM

chat

Send prompts to CrowLLM models and return replies with token usage for OpenAI-compatible model access and cost tracking.

Instructions

Send a prompt to any CrowLLM model (POST /v1/chat/completions) and return the reply with token usage.

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

Input Schema

NameRequiredDescriptionDefault
modelYesModel id, e.g. deepseek-v4-flash
promptYesUser message
systemNoOptional system message
max_tokensNo
temperatureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the HTTP method/endpoint and that the response contains the reply plus token usage, but says nothing about authentication requirements, rate limits, cost implications, streaming behavior, or what happens on invalid model ids.

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

Conciseness5/5

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

One sentence, front-loaded with the action, with the endpoint and return value appended. No filler or redundancy.

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

Completeness3/5

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

For a 5-parameter, no-annotation, no-output-schema tool, the description covers purpose and the rough return shape but leaves generation-control semantics, model-id discovery, and operational constraints (auth, limits) unaddressed. Adequate to make the call, thin for making it correctly.

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 60%: model, prompt, and system are documented in the schema, while max_tokens and temperature carry only min/max constraints with no meaning in either place. The description adds no parameter-level information at all, so it fails to compensate for the two undocumented generation controls.

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?

States a specific verb and resource ('Send a prompt to any CrowLLM model') and identifies the underlying endpoint (POST /v1/chat/completions), so the agent knows this is a chat-completion call. It does not explicitly contrast itself with siblings like search_models or get_pricing, but the verbs/resources are disjoint enough that confusion is unlikely.

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

Usage Guidelines3/5

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

Usage is implied by 'send a prompt to any CrowLLM model' and the endpoint reference, but there is no explicit when-to-use rule, no mention of using search_models to discover a valid model id, and no guidance on when to supply system/temperature/max_tokens versus omitting them.

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