Skip to main content
Glama

get_ai_model_providers

Read-only

Maps each Now Assist skill and AI agent capability to its LLM provider, returning provider configuration, routing, preferences, and model mappings for AI governance and data residency reviews.

Instructions

Which LLM provider each Otto (Now Assist) skill and AI agent capability uses: the default, active OneExtend definition per capability (sys_one_extend_definition_config), grouped by provider (Now LLM, Azure OpenAI, AWS Claude, Google Gemini and others). Also returns the configured providers (sys_gen_ai_provider, OEM or BYOK), provider routing and preferences, recent preference changes, model availability and version mappings, Guardian providers, and agents by strategy. From July 2026 out-of-box skills default to third-party providers, so use this for data residency and AI governance reviews. Read-only.

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_ai_model_providers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax skills to list (default 50, max 500). Totals by provider always cover every skill
skillNoOnly skills or capabilities whose name contains this text
providerNoOnly skills whose provider contains this text, e.g. "Azure", "Claude", "Now LLM"
agents_onlyNoOnly the AI Agents capabilities (scope sn_aia)
summary_onlyNoReturn the totals by provider and the configuration, without the per-skill list (much smaller)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so 'Read-only' in the description is redundant. Beyond that, the description adds genuinely useful behavior: it enumerates the broad set of configuration surfaces returned, and notes that provider totals always cover every skill even when 'limit' truncates the per-skill list. It still doesn't hint at cost or latency despite the wide fan-out.

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

Conciseness3/5

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

The main purpose is front-loaded in the first clause, which is good. But the second sentence is a long unpunctuated laundry list of returned objects (providers, routing, preference changes, model mappings, Guardian providers, agents by strategy) that is hard to parse and partly duplicates what the next sentence implies.

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 five optional parameters and no output schema, the description carries the burden of describing returns, and it does so in detail, including the filter-versus-totals interaction and the governance framing. Minor gaps remain around pagination or result ordering, but the tool is adequately covered.

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 every parameter (limit, skill, provider, agents_only, summary_only) is already documented in the schema with defaults and maxima. The description adds no parameter-specific meaning, 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 opening clause names a specific verb and resource: which LLM provider each Otto/Now Assist skill and AI agent capability uses, with the underlying table (sys_one_extend_definition_config) identified. It does not explicitly contrast itself with any sibling tool (e.g. get_ai_agent or get_ai_usage), so it stops short of a 5.

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?

It gives one concrete use case (data residency and AI governance reviews) and flags the July 2026 default-provider change as context, which implies when the tool matters. However, it never says when NOT to use it or which sibling to pick for adjacent questions, and it gives no prerequisites or exclusions.

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