Skip to main content
Glama
Sign In

Omnara

by com.omnara
OverviewDiscussions(1)Admin

List configured models

models_list
Read-onlyIdempotent

Lists the models configured under one model provider config, newest first, with each model's slug, token limits, and reasoning support.

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": {
      "modelProviderConfigID": "<modelProviderConfigID>",
      "orgID": "<orgID>"
    },
    "name": "models_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of items to return in one page.
orgIDYesOrganization ID (org_...).
cursorNoOpaque pagination cursor from a previous response's next_cursor. Omit for the first page.
modelProviderConfigIDYesModel provider config ID (mpc_...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / modelProviderConfigID / description
      Added value: +"Model provider config ID (mpc_...)."
    • addedInput schema / properties / orgID / description
      Added value: +"Organization ID (org_...)."
  2. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine context beyond that: the newest-first ordering and the per-item payload (slug, token limits, reasoning support), which matters because there is no output schema. Pagination behavior is left to the schema rather than described.

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?

A single front-loaded sentence with no filler; ordering, scope, and returned fields are packed in without redundancy.

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 full schema coverage, no output schema, and annotations carrying the safety profile, the description supplies the return-field content the agent otherwise could not know. Pagination is deferred entirely to the schema, which is a minor gap rather than a missing requirement.

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 limit, cursor, orgID, and modelProviderConfigID are fully documented structurally. The description adds only the implicit notion that results are scoped to one provider config; it does not clarify cursor/limit semantics 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.

Purpose4/5

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

States a specific verb ("Lists") plus resource and scope ("models configured under one model provider config"), which separates it from models_create/update/delete and model_providers_list. It stops short of explicitly naming the sibling it is not, so it lacks the active sibling differentiation that would earn 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 Guidelines2/5

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

There is no when-to-use / when-not-to-use guidance and no mention of neighboring tools such as model_providers_catalog or grant_models_list. The provider-config scoping is the only cue about appropriate use, which is thin given how many list-style siblings exist.

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

All Omnara toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources