Skip to main content
Glama
Local AI MCP

Local AI MCP

Official
by TMHSDigital

Suggest model

suggest_model
Read-onlyIdempotent

Recommends catalog models for a task, ranked by fit to your machine's GPU and CPU capacity. Explains each pick and flags models already installed on a live provider.

Instructions

Recommend catalog models for a task, ranked for THIS machine: fully-on-GPU first, then partial GPU offload, then CPU-only. Within a tier the largest (most capable) model comes first unless preferSpeed is true. Flags models already installed on a live provider and explains each pick.

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

Input Schema

NameRequiredDescriptionDefault
taskYesThe task you want a model for
kvCacheTypeNoKV cache precision (default f16)
preferSpeedNoPrefer smaller, faster models within each tier
contextLengthNoContext length to plan for (default 4096)

Output Schema

NameRequiredDescriptionDefault
taskYes
suggestionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / contextLength
      Added value: +{
      +  "description": "Context length to plan for (default 4096)",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
    • addedInput schema / properties / kvCacheType
      Added value: +{
      +  "description": "KV cache precision (default f16)",
      +  "enum": [
      +    "f16",
      +    "q8_0",
      +    "q4_0"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / preferSpeed
      Added value: +{
      +  "description": "Prefer smaller, faster models within each tier",
      +  "type": "boolean"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "suggestions": {
      +      "items": {
      +        "additionalProperties": {},
      +        "propertyNames": {
      +          "type": "string"
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "task": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "task",
      +    "suggestions"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.4.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare this is a safe, idempotent, closed-world read, so the safety profile needs no restating. The description adds real behavioral value beyond that: the exact ranking order (full GPU → partial offload → CPU), the within-tier tie-break, and that installed models are flagged on a live provider.

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?

Three dense sentences, front-loaded with purpose then ranking rules then output traits. No filler and every clause carries information an agent needs to interpret results.

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

Completeness5/5

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

With an output schema present, return values need no explanation, and the description still covers the semantics of the ranking, the tie-break, and the installed-model flag. Nothing an agent needs in order to call and interpret this correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the four parameters are already documented and 3 would be the baseline. The description earns one more point by explaining how preferSpeed actually interacts with tier ordering ('largest comes first unless preferSpeed is true'), which the schema's one-liner does not make explicit.

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?

States a specific verb and resource ('Recommend catalog models for a task') plus the key differentiator: ranked for THIS machine. An agent can separate this from list_models, list_available, or fit_check without opening any schema.

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?

Clear context for when to call it (you have a task and want a ranked recommendation), and the tiering rules imply it is the right tool when hardware fit matters. It never names an alternative such as fit_check or list_models, nor states exclusions, so it stops short of a 5.

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