Skip to main content
Glama
Sign In
Anam MCP Server

Anam MCP Server

Official
by anam-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_llms

Retrieve a paginated list of all available large language models. Specify page number and items per page to control output.

Instructions

List all available LLMs.

Args: page: Page number (default: 1) per_page: Items per page (default: 100)

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

Input Schema

NameRequiredDescriptionDefault
pageNo
per_pageNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.13

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states 'List all available LLMs' and repeats parameter names, failing to disclose any behavioral traits such as pagination behavior, rate limits, or what happens if there are no results.

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 to the point, but includes 'Args:' section which is slightly beyond pure conciseness. Overall, it is efficient without wasted words.

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

Completeness3/5

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

Given the simple two-parameter input and existence of an output schema, the description is minimally adequate. However, it lacks details on pagination, sorting, or authentication, which would be helpful for a complete understanding.

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 has 0% description coverage, but the description adds minimal context by stating default values and parameter names (page, per_page). This adds some meaning beyond the schema, but not enough to fully compensate.

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 clearly states 'List all available LLMs' with a specific verb and resource. It distinguishes itself from sibling tools like create_llm, get_llm, and update_llm, which perform different actions on LLMs.

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?

No guidance is provided on when to use this tool versus other list operations (e.g., list_avatars, list_sessions) or alternatives like search_llm. The description lacks context for appropriate usage.

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