Skip to main content
Glama
LMPrado-DZ23

DZ23 Subagents Universal MCP

by LMPrado-DZ23
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Discover models

discover_models
Read-only

Query provider model catalogs to discover which AI models are offered, with results cached for five minutes. Refresh bypasses cache; cache-only returns cached entries without contacting providers.

Instructions

Query provider /models catalogs (cached five minutes). A catalog entry does not prove inference access.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refreshNoBypass the five-minute catalog cache.
providerNoLimit discovery to one provider.
cache_onlyNoReturn cached catalogs only; never contact a provider.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.1.0
    • addedInput schema / properties / cache_only
      Added value: +{
+  "default": false,
+  "description": "Return cached catalogs only; never contact a provider.",
+  "type": "boolean"
+}
  2. Changed6 schema fields changedv3.0.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / provider / description
      Added value: +"Limit discovery to one provider."
    • addedInput schema / properties / provider / pattern
      Added value: +"^[a-z0-9][a-z0-9_-]{0,39}$"
    • addedInput schema / properties / provider / x-pattern-reason
      Added value: +"must be a registered provider name"
    • addedInput schema / properties / refresh / default
      Added value: +false
    • addedInput schema / properties / refresh / description
      Added value: +"Bypass the five-minute catalog cache."
  3. First observedv2.2.4

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only and non-destructive behavior. The description adds caching TTL ('cached five minutes') and the important caveat that catalog presence does not guarantee inference access, which is useful 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.

Conciseness5/5

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

Two sentences, front-loaded with the core action and resource, followed by a concise caveat. No wasted words.

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 discovery tool with optional parameters and safety covered by annotations, the description covers cache behavior and a critical semantic caveat. It doesn't explicitly address sibling distinctions (list_models/verify_model), but that is a minor gap.

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 all parameters are documented in the schema. The description adds little beyond the schema, except reinforcing the five-minute cache context, which the schema already mentions. 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?

Description states a specific verb (query) and resource (provider /models catalogs) and includes a key semantic caveat about inference access, which distinguishes it from siblings like list_models and verify_model.

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 clearly implies the tool is for querying provider catalogs, and the caveat about inference access hints that verification is separate (suggesting verify_model), but it does not explicitly name alternatives or exclusion conditions.

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