Skip to main content
Glama
phuihock
by phuihock

token_classification

Identify and classify named entities in text using natural language processing. Extract people, organizations, locations, and other entities from documents for data analysis.

Instructions

Perform token classification (NER) using DeepInfra OpenAI-compatible API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Main handler function for the 'token_classification' tool. It uses a prompted language model completion to perform named entity recognition (NER) on input text.
        @app.tool()
        async def token_classification(text: str) -> str:
            """Perform token classification (NER) using DeepInfra OpenAI-compatible API."""
            model = DEFAULT_MODELS["token_classification"]
            prompt = f"""Perform named entity recognition on the following text. Identify all named entities (persons, organizations, locations, dates, etc.) and classify them. Provide your analysis in JSON format with an array of entities, each having 'entity', 'type', and 'position' fields.
    
    Text: {text}
    
    Response format: {{"entities": [{{"entity": "entity_name", "type": "PERSON/ORG/LOC/DATE/etc", "position": [start, end]}}]}}"""
            try:
                response = await client.completions.create(
                    model=model,
                    prompt=prompt,
                    max_tokens=500,
                    temperature=0.1,
                )
                if response.choices:
                    return response.choices[0].text
                else:
                    return "Unable to perform token classification"
            except Exception as e:
                return f"Error performing token classification: {type(e).__name__}: {str(e)}"
  • Conditional registration of the token_classification tool using the @app.tool() decorator on the FastMCP app.
    if "all" in ENABLED_TOOLS or "token_classification" in ENABLED_TOOLS:
        @app.tool()
  • Default models configuration dictionary, including the model used for token_classification (default: 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"),
    }
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 states the action and API but lacks details on rate limits, authentication needs, error handling, or what the tool returns. For a tool with no annotations and an output schema, this leaves significant gaps in understanding its behavior.

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 no wasted words. It front-loads the core purpose and includes relevant API context, making it appropriately sized and well-structured for quick comprehension.

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 moderate complexity (NER task with one parameter) and the presence of an output schema, the description is minimally complete. It covers the basic purpose and API but lacks usage guidelines, behavioral details, and parameter semantics, leaving the agent reliant on the output schema for return values.

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 0%, so the description must compensate. It implies the 'text' parameter is for input to the NER model but doesn't elaborate on format, length constraints, or language requirements. The description adds minimal value beyond what the schema's title ('Text') suggests, resulting in an adequate but incomplete parameter understanding.

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 action ('Perform token classification (NER)') and specifies the resource ('using DeepInfra OpenAI-compatible API'), which distinguishes it from siblings like text_classification or text_generation. However, it doesn't explicitly differentiate token classification from other NLP tasks in the sibling list beyond the NER acronym.

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 like text_classification or other siblings. It mentions the API but doesn't specify use cases, prerequisites, or exclusions, leaving the agent to infer usage from the tool 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/phuihock/mcp-deeinfra'

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