Skip to main content
Glama
phuihock
by phuihock

text_classification

Classify text into categories using DeepInfra's AI models. Input text to receive structured classification results for analysis and organization.

Instructions

Classify text using DeepInfra OpenAI-compatible API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'text_classification' tool, registered via @app.tool(). It crafts a prompt for text classification (sentiment and category) using the configured model via DeepInfra's OpenAI-compatible completions API and returns the model's response.
        @app.tool()
        async def text_classification(text: str) -> str:
            """Classify text using DeepInfra OpenAI-compatible API."""
            model = DEFAULT_MODELS["text_classification"]
            prompt = f"""Analyze the following text and classify it. Determine the sentiment (positive, negative, neutral) and main category/topic. Provide your analysis in JSON format with 'sentiment' and 'category' fields.
    
    Text: {text}
    
    Response format: {{"sentiment": "positive/negative/neutral", "category": "topic"}}"""
            try:
                response = await client.completions.create(
                    model=model,
                    prompt=prompt,
                    max_tokens=200,
                    temperature=0.1,
                )
                if response.choices:
                    return response.choices[0].text
                else:
                    return "Unable to classify text"
            except Exception as e:
                return f"Error classifying text: {type(e).__name__}: {str(e)}"
  • Configuration dictionary for default models used by tools, including the model for 'text_classification' (defaults to 'microsoft/DialoGPT-medium').
    DEFAULT_MODELS = {
        "generate_image": os.getenv("MODEL_GENERATE_IMAGE", "Bria/Bria-3.2"),
        "text_generation": os.getenv("MODEL_TEXT_GENERATION", "meta-llama/Llama-2-7b-chat-hf"),
        "embeddings": os.getenv("MODEL_EMBEDDINGS", "sentence-transformers/all-MiniLM-L6-v2"),
        "speech_recognition": os.getenv("MODEL_SPEECH_RECOGNITION", "openai/whisper-large-v3"),
        "zero_shot_image_classification": os.getenv("MODEL_ZERO_SHOT_IMAGE_CLASSIFICATION", "openai/gpt-4o-mini"),
        "object_detection": os.getenv("MODEL_OBJECT_DETECTION", "openai/gpt-4o-mini"),
        "image_classification": os.getenv("MODEL_IMAGE_CLASSIFICATION", "openai/gpt-4o-mini"),
        "text_classification": os.getenv("MODEL_TEXT_CLASSIFICATION", "microsoft/DialoGPT-medium"),
        "token_classification": os.getenv("MODEL_TOKEN_CLASSIFICATION", "microsoft/DialoGPT-medium"),
        "fill_mask": os.getenv("MODEL_FILL_MASK", "microsoft/DialoGPT-medium"),
    }
  • Conditional registration of the text_classification tool based on ENABLED_TOOLS environment variable.
    if "all" in ENABLED_TOOLS or "text_classification" in ENABLED_TOOLS:
        @app.tool()
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the API provider (DeepInfra) but doesn't describe traits like rate limits, authentication needs, output format, or error handling. This leaves significant gaps for a tool that interacts with an external service.

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, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly.

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 complexity (external API call), no annotations, and an output schema present, the description is minimally adequate. It identifies the API but lacks details on behavior, parameters, or usage context, making it incomplete for safe and effective tool invocation.

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 input schema has 0% description coverage, but the description adds no parameter semantics beyond implying 'text' is the input. It doesn't explain what types of text are suitable, length constraints, or expected formats, so it doesn't compensate for the schema's lack of documentation.

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 clearly states the verb 'Classify' and the resource 'text', specifying it uses the DeepInfra OpenAI-compatible API. However, it doesn't differentiate from sibling tools like 'zero_shot_image_classification' or 'token_classification', which might also involve classification tasks but for different data types or methods.

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 sibling tools like 'text_generation' or 'embeddings', nor does it specify use cases, prerequisites, or exclusions for text classification.

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/phuihock/mcp-deeinfra'

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