Skip to main content
Glama

Recommend model

recommend_model
Read-onlyIdempotent

Suggests a local model for your use case by matching hardware fit and 30-day Studio usage, returning a JSON recommendation and hardware summary.

Instructions

Recommend a local model from hardware fit, then 30-day Studio usage when it still fits. Use get_hardware_profile for the raw numbers. Use install_model to pull the pick. Read-only. Returns JSON with the recommendation and a hardware summary.

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": "recommend_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
use_caseNoIntended use. One of general, coding, chat, summarisation, or a short free-text use case. Default general.general

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv6.2.1
    • addedInput schema / properties / use_case / description
      Added value: +"Intended use. One of general, coding, chat, summarisation, or a short free-text use case. Default general."
  2. Changed1 schema field changedv6.2.0
    • addedInput schema / properties / use_case
      Added value: +{
      +  "default": "general",
      +  "title": "Use Case",
      +  "type": "string"
      +}
  3. First observedv5.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds the substantive behavior: recommendations are derived first from hardware fit and then from 30-day Studio usage, which is useful context beyond the annotations.

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?

The description is short and front-loaded with the core recommendation logic. The final sentence explaining return shape is somewhat redundant because an output schema exists, so it is not maximally efficient.

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?

With annotations, an output schema, and full parameter documentation, the description provides enough context to invoke the tool correctly. The domain-specific phrase '30-day Studio usage' could be clearer, but it is not essential to selection or invocation.

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?

The schema description coverage is 100%, and the single use_case parameter is already documented with allowed values and a default. The description does not add any parameter-level guidance beyond the schema, so the baseline 3 applies.

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

Purpose5/5

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

The description states a specific verb and resource, then adds the exact recommendation basis: hardware fit followed by 30-day Studio usage. It is clearly distinguishable from list_models and get_hardware_profile, which the description explicitly contrasts.

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

Usage Guidelines4/5

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

It routes the agent to get_hardware_profile for raw numbers and install_model for installation, making the intended workflow clear. It lacks an explicit 'do not use this when...' exclusion, but the alternatives are named and contextualized.

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