Skip to main content
Glama

listTextModels

Retrieve available text generation models for AI assistants to create content through the Pollinations API without authentication.

Instructions

List available text models

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function that fetches and returns the list of available text models from the Pollinations Text API.
    export async function listTextModels() {
      try {
        const response = await fetch('https://text.pollinations.ai/models');
    
        if (!response.ok) {
          throw new Error(`Failed to list text models: ${response.statusText}`);
        }
    
        const models = await response.json();
        return { models };
      } catch (error) {
        log('Error listing text models:', error);
        throw error;
      }
    }
  • Input/output schema definition for the listTextModels tool. No input parameters required.
    export const listTextModelsSchema = {
      name: 'listTextModels',
      description: 'List available text models',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    };
  • Registers the tool schema by including it in the list of tools returned for ListToolsRequest.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: getAllToolSchemas()
    }));
  • Dispatch handler in MCP CallToolRequest that invokes the listTextModels function for this tool name.
    } else if (name === 'listTextModels') {
      try {
        const result = await listTextModels();
        return {
          content: [
            { type: 'text', text: JSON.stringify(result, null, 2) }
          ]
        };
      } catch (error) {
        return {
          content: [
            { type: 'text', text: `Error listing text models: ${error.message}` }
          ],
          isError: true
        };
      }
  • src/schemas.js:42-42 (registration)
    Includes the listTextModelsSchema in the getAllToolSchemas() array used for tool listing.
    listTextModelsSchema
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 of behavioral disclosure. It states the action ('List') but doesn't describe traits like whether it's read-only (implied by 'List'), potential side effects, authentication requirements, rate limits, or output format. For a tool with zero annotation coverage, this is a significant gap in transparency, though it doesn't contradict any 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?

The description is a single, clear sentence with no wasted words: 'List available text models'. It is front-loaded and efficiently conveys the core purpose without unnecessary elaboration. Every word earns its place, making it highly concise and well-structured for a simple tool.

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 tool's low complexity (0 parameters, no output schema, no annotations), the description is minimally complete. It states what the tool does but lacks context on usage, behavior, or output. For a simple list operation, this might be adequate, but it doesn't provide enough guidance for an agent to use it effectively without additional inference, especially with siblings present.

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?

The input schema has 0 parameters with 100% coverage (empty object), so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate given the schema's completeness. Baseline for high schema coverage is 3, but with zero parameters, the description's lack of param info is not a deficiency, warranting a higher score for adequacy.

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 description 'List available text models' clearly states the verb ('List') and resource ('available text models'), making the purpose immediately understandable. It distinguishes from siblings like 'listImageModels' and 'listAudioVoices' by specifying 'text' models, though it doesn't explicitly contrast with them. The description is not tautological (it adds 'available' beyond the name) but lacks specificity about scope or format.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., authentication), context for usage (e.g., before generating text), or exclusions (e.g., not for editing). With siblings like 'respondText' for text generation, the lack of comparative guidance leaves the agent to infer usage based on name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pinkpixel-dev/MCPollinations'

If you have feedback or need assistance with the MCP directory API, please join our Discord server