Skip to main content
Glama
crowllm-mcp

crowllm-mcp

Official
by crowwdev

CrowLLM pricing

get_pricing

Retrieve CrowLLM model list prices in USD per 1M tokens, including calculated input and output costs, with optional name filtering and free-only results.

Instructions

List CrowLLM list prices in USD per 1M tokens. Input = 2 x model_ratio; output = input x completion_ratio.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows (default 50)
queryNoSubstring to match against model names
free_onlyNoOnly zero-rated rows

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the return semantics that matter most here (list prices denominated in USD per 1M tokens), implying a read-only lookup. It omits ordering, pagination/default behavior, and what the ratio formula means for the agent, and the formula itself is too cryptic to count as disclosure.

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

Conciseness4/5

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

Two short sentences, front-loaded with the core statement of what is listed and in what units. The second sentence is compact but cryptic enough that it does not fully earn its place.

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

Completeness4/5

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

For a simple read-only pricing list with three optional, fully documented parameters and no output schema, the description covers the essential facts. Gaps are minor: default row count and result ordering are left to the schema or unstated.

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

Parameters3/5

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

Schema description coverage is 100%, so limit, query, and free_only are already fully documented in the schema, making 3 the baseline. The description adds nothing about these parameters; the "Input = ..." sentence appears to describe pricing arithmetic rather than the tool's input arguments, so it risks being misread as parameter guidance.

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 first sentence gives a specific verb plus resource plus unit: "List CrowLLM list prices in USD per 1M tokens," which is enough to distinguish a pricing lookup from the chat and search_models siblings. The second sentence, however, is opaque ("Input = 2 x model_ratio; output = input x completion_ratio") and reads like a pricing formula rather than a statement of purpose, slightly blurring the intent.

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 offers no when-to-use guidance, no prerequisites, and never names an alternative such as search_models for discovering models before looking up prices. Usage is only implied by the word "List."

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