Skip to main content
Glama
Sign In
Axis MCP

Axis MCP

by hemla-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

add_text_overlay

Idempotent

Add text overlays to video streams, including dynamic date and time via format modifiers for real-time information display.

Instructions

Add a text overlay to the video stream. Supports format modifiers like %F (date), %T (time).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "add_text_overlay"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoX position (used if position not set)
yNoY position (used if position not set)
textYesOverlay text (supports modifiers: %F=date, %T=time, %X=time, %x=date)
colorNoText color (e.g. white, black, red)
cameraNoCamera/channel (default 0)
fontSizeNoFont size
positionNoNamed position: topLeft, topRight, bottomLeft, bottomRight, top, bottom
backgroundColorNoBackground color (e.g. transparent, black)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description's indication of a write operation is consistent. It adds value by mentioning format modifiers, but does not disclose whether multiple overlays can be added or if it replaces existing ones.

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?

Two concise sentences with no wasted words. The main action is front-loaded, and the format modifier example is efficiently included.

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?

The description lacks information about the overlay's lifecycle (e.g., persistence, visibility), and does not explain return behavior. Given no output schema, this missing context reduces completeness.

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 100%, so the schema already documents all parameters. The description adds minor context about format modifiers for the 'text' parameter, but does not significantly enhance understanding beyond the schema.

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 the action (add) and resource (text overlay to video stream). It distinguishes from sibling tools like get_overlay and remove_overlay, making the purpose unambiguous.

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, nor does it mention scenarios where it should not be used or prerequisites like existing overlays.

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