Skip to main content
Glama

dense_caption

Generate detailed captions for images from URLs or local files to describe visual content using computer vision models.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathNo
image_urlNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler function for 'dense_caption'. Validates image input (URL or file path) and calls the runner function.
    @mcp.tool()
    def dense_caption(
        image_url: Optional[str] = None,
        file_path: Optional[str] = None,
    ) -> str:
        if not image_url and not file_path:
            raise ValueError("Provide either image_url or file_path")
        if image_url and file_path:
            raise ValueError("Provide only one of image_url or file_path, not both")
        image_ref = image_url or file_path  # type: ignore
        return run_dense_caption(image_ref)
  • Core logic for generating dense captions using local, Ollama, or OpenRouter backends with specific prompts.
    def run_dense_caption(image_ref: str, *, model: Optional[str] = None) -> str:
        if _use_local_for("caption"):
            prompt = f"{prompts.CAPTION_SYSTEM}\n\n{prompts.CAPTION_USER}"
            return _local_gen(image_ref, prompt)
        if _use_ollama_for("caption"):
            from cv_mcp.captioning.ollama_client import OllamaClient
            client = OllamaClient(host=str(_cfg_value("ollama_host", "http://localhost:11434")))
            res = client.analyze_single_image(
                image_ref,
                prompts.CAPTION_USER,
                model=_cfg_value("caption_model"),
                system=prompts.CAPTION_SYSTEM,
            )
            if not res.get("success"):
                raise RuntimeError(str(res.get("error", "Dense caption generation failed (ollama)")))
            return str(res.get("content", "")).strip()
        client = OpenRouterClient()
        res = client.analyze_single_image(
            image_ref,
            prompts.CAPTION_USER,
            model=model or _cfg_value("caption_model"),
            system=prompts.CAPTION_SYSTEM,
        )
        if not res.get("success"):
            raise RuntimeError(str(res.get("error", "Dense caption generation failed")))
        return str(res.get("content", "")).strip()
  • Prompt templates (system and user) specifically for dense caption generation.
    CAPTION_SYSTEM = (
        "You carefully describe visual content without guessing. Mention salient text only if clearly readable."
    )
    
    CAPTION_USER = (
        "Write a factual, detailed caption (2–6 sentences) for this image. Cover:\n"
        "- Who/what is visible (counts if reliable).\n"
        "- Where/setting if visually indicated.\n"
        "- Salient readable text.\n"
        "- Relationships (e.g., 'person holding red umbrella near taxi').\n"
        "- Lighting/time cues if obvious (e.g., night, golden hour).\n"
        "If uncertain, say 'unclear'. Do not guess brands, species, or locations unless unmistakable. Avoid subjective adjectives."
    )
  • The @mcp.tool() decorator registers this function as the 'dense_caption' tool in the FastMCP server.
    @mcp.tool()
    def dense_caption(
        image_url: Optional[str] = None,
        file_path: Optional[str] = None,
    ) -> str:
        if not image_url and not file_path:
            raise ValueError("Provide either image_url or file_path")
        if image_url and file_path:
            raise ValueError("Provide only one of image_url or file_path, not both")
        image_ref = image_url or file_path  # type: ignore
        return run_dense_caption(image_ref)
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

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

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

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

Tool has no description.

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/samhains/cv-mcp'

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