Skip to main content
Glama

median_price_by_task

Read-only

The typical (median) current price of a job (task) across models, and the n models closest to it - what a normal price for this job is. Same arguments as cheapest_models_by_task.

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": {
      "task": "<task>"
    },
    "name": "median_price_by_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNo10 by default
taskYeswhat the buyer wants done: text (chat/LLM), vision, image, video, tts (speech from text), stt (text from speech), embedding, rerank, moderation - a job, not a model type (search_offers' category is the model type)
scopeNoall (default), specialized (the task's own category) or multi/universal (qualifying llm models - the two names mean the same set, WP-0086)
componentNoinput_tokens (default), output_tokens, or the task's own unit

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / task / enum
      Previous value: -[
      -  "embedding",
      -  "image",
      -  "moderation",
      -  "rerank",
      -  "stt",
      -  "text",
      -  "tts",
      -  "video",
      -  "vision"
      -]New value: +[
      +  "decision",
      +  "embedding",
      +  "image",
      +  "moderation",
      +  "rerank",
      +  "stt",
      +  "text",
      +  "tts",
      +  "video",
      +  "vision"
      +]
  2. Added

TDQS

B3.4/5.0
Behavior3/5

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

readOnlyHint=true already establishes the safety profile, so the description's added value is the return composition: a median figure plus the n models nearest that median. It does not say how "closest" is measured (presumably by price), in what order results come back, or what currency/unit the median is expressed in, so the behavioral picture remains partial.

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, the core metric front-loaded and the "normal price" framing placed as a trailing gloss. Slight redundancy between "typical (median)" and the gloss, but nothing extraneous enough to cut.

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?

With no output schema, the description is the only source for return shape, and it only sketches it (median plus n nearby models) without field-level detail or units. For a read-only lookup with fully documented parameters this is workable but leaves an agent guessing about the exact response contents.

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%, and the schema itself already explains task (job vs. model type, with a pointer to search_offers' category), scope, component and the n default. The description adds no parameter meaning beyond the cross-reference "Same arguments as cheapest_models_by_task," so the baseline 3 applies.

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 typical (median) current price of a job (task) across models, and the n models closest to it" names a specific metric, resource and companion return set, which naturally separates it from cheapest_models_by_task and most_expensive_models_by_task. The closing gloss "what a normal price for this job is" reinforces the intent, though the contrast with the cheapest/expensive siblings is only implied by the metric name rather than stated.

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: pick this when you want a representative/benchmark price rather than an extreme. There is no explicit when-to-use or when-not, and the only routing hint is "Same arguments as cheapest_models_by_task," which points at a sibling's interface, not at a decision rule for choosing between them.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources