Axis MCP

by hemla-com

Overview Schema Source Related Servers Discussions Admin

TypeScript

update_stream_profile

Idempotent

Modify the parameters and description of an existing stream profile to adjust video stream settings.

Instructions

Update an existing stream profile.

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": {
      "name": "<name>",
      "parameters": "<parameters>"
    },
    "name": "update_stream_profile"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Profile name to update
`parameters`	Yes	New stream parameters
`description`	No	New description

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Jul 28, 2026

TDQS

B3.2/5.0

Behavior2/5

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

Annotations provide readOnlyHint=false, openWorldHint=true, idempotentHint=true, destructiveHint=false. Description adds no extra behavioral context beyond these, such as side effects or overwrite behavior.

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

Conciseness4/5

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

Single sentence, front-loaded, no wasted words. However, could incorporate more context without becoming verbose.

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 simplicity of the operation and annotations, description is fairly complete but lacks explicit mention of precondition (profile existence) or failure modes.

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 coverage is 100% with descriptions for all 3 parameters. Description does not add additional meaning 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?

Description states 'Update an existing stream profile' with clear verb and resource. It distinguishes from siblings like create_stream_profile and remove_stream_profile, which handle creation and deletion.

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?

No guidance on when to use vs alternatives, prerequisites (profile must exist), or when not to use. The description is minimal and lacks context.

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