Skip to main content
Glama
Blazemeter

BlazeMeter Service Virtualization MCP Server

Official
by Blazemeter

virtual_services_tracking

Poll tracking status by UUID to get the completion state, errors, and results of virtual service operations like deployment, configuration, and asset uploads.

Instructions

    Operations on tracking objects.
    Use this tool to read or poll tracking status by tracking ID (UUID).
    Call this whenever you have a tracking ID and need to know the status or result of an async operation.
    Actions:
    - read: Read a Tracking. Get status and result of a virtual service deploy/stop/configure operation.
        args(dict): Dictionary with the following required parameters:
            tracking_id (str): Mandatory. The tracking UUID to read.
    - read_asset_tracking: Read an Asset Tracking. Get the status and result of an asset upload operation.
        Use this action — NOT `read` — when the tracking ID came from an asset upload (e.g. "read asset tracking info <uuid>").
        args(dict): Dictionary with the following required parameters:
            tracking_id (str): Mandatory. The tracking UUID to read.
    Tracking Schema:
    {'$defs': {'DeploymentTracking': {'properties': {'trackingId': {'default': None, 'description': 'Tracking id. Must be valid UUID string.', 'title': 'Trackingid', 'type': 'string'}, 'status': {'default': None, 'description': "Tracking status. Must be one of the values: 'PENDING', 'RUNNING', 'FINISHED'.", 'title': 'Status', 'type': 'string'}, 'errors': {'anyOf': [{'items': {'type': 'string'}, 'type': 'array'}, {'type': 'null'}], 'default': None, 'description': 'List of errors.', 'title': 'Errors'}, 'warnings': {'anyOf': [{'items': {'type': 'string'}, 'type': 'array'}, {'type': 'null'}], 'default': None, 'description': 'List of warnings.', 'title': 'Warnings'}, 'data': {'anyOf': [{'$ref': '#/$defs/DeploymentTrackingData'}, {'type': 'null'}], 'default': None, 'description': 'Deployment Tracking data.'}}, 'title': 'DeploymentTracking', 'type': 'object'}, 'DeploymentTrackingData': {'properties': {'dataType': {'default': 'DEPLOYMENT', 'description': "Tracking data type. Constant value: 'DEPLOYMENT'.", 'title': 'Datatype', 'type': 'string'}, 'serviceMockId': {'default': None, 'description': 'Virtual service id.', 'title': 'Servicemockid', 'type': 'integer'}, 'stage': {'default': None, 'description': 'Current stage of the tracked job.', 'title': 'Stage', 'type': 'string'}, 'started': {'default': None, 'description': 'Unix timestamp of the stage start moment.', 'title': 'Started', 'type': 'integer'}}, 'title': 'DeploymentTrackingData', 'type': 'object'}, 'MasterTrackingData': {'properties': {'dataType': {'default': 'MASTER_TRACKING', 'description': "Tracking data type. Constant value: 'MASTER_TRACKING'.", 'title': 'Datatype', 'type': 'string'}, 'serviceMockTrackingDtos': {'anyOf': [{'items': {'$ref': '#/$defs/ServiceMockTrackingDto'}, 'type': 'array'}, {'type': 'null'}], 'default': None, 'description': 'List of subtrackings of the Virtual services related to the job.', 'title': 'Servicemocktrackingdtos'}}, 'title': 'MasterTrackingData', 'type': 'object'}, 'ServiceMockTrackingDto': {'properties': {'serviceMockId': {'default': None, 'description': 'Virtual service id.', 'title': 'Servicemockid', 'type': 'integer'}, 'serviceMockName': {'default': None, 'description': 'Virtual service name.', 'title': 'Servicemockname', 'type': 'string'}, 'started': {'default': None, 'description': 'Unix timestamp of the stage start moment.', 'title': 'Started', 'type': 'integer'}, 'trackingDto': {'anyOf': [{'$ref': '#/$defs/DeploymentTracking'}, {'type': 'null'}], 'default': None, 'description': 'Deployment Tracking object.'}}, 'title': 'ServiceMockTrackingDto', 'type': 'object'}}, 'properties': {'trackingId': {'default': None, 'description': 'Tracking id. Must be valid UUID string.', 'title': 'Trackingid', 'type': 'string'}, 'status': {'default': None, 'description': "Tracking status. Must be one of the values: 'PENDING', 'RUNNING', 'FINISHED'.", 'title': 'Status', 'type': 'string'}, 'errors': {'anyOf': [{'items': {'type': 'string'}, 'type': 'array'}, {'type': 'null'}], 'default': None, 'description': 'List of errors.', 'title': 'Errors'}, 'warnings': {'anyOf': [{'items': {'type': 'string'}, 'type': 'array'}, {'type': 'null'}], 'default': None, 'description': 'List of warnings.', 'title': 'Warnings'}, 'data': {'anyOf': [{'$ref': '#/$defs/MasterTrackingData'}, {'type': 'null'}], 'default': None, 'description': 'Deployment Tracking data.'}}, 'title': 'MasterTracking', 'type': 'object'}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsYes
actionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
infoNoInfo messages
errorNoError message
totalNoTotal available records
resultNoResult
warningNoWarning messages
has_moreNoMore records per page to list
Behavior5/5

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

With no annotations, the description carries full responsibility for disclosing behavior. It details what each action returns (status, result, errors, warnings), the possible tracking statuses ('PENDING', 'RUNNING', 'FINISHED'), and the structure of the tracking data. This transparency helps the agent predict outcomes without additional heuristics.

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 well-structured, starting with a clear one-line purpose, then breaking down actions and parameters, and finally providing the detailed tracking schema. While long, every part contributes value and is organized logically. The front-loaded summary makes it easy to grasp the tool's core purpose quickly.

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

Completeness5/5

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

The description fully covers the tool's scope: two distinct actions, their use cases, required parameters, and the full response schema (including nested objects like DeploymentTracking and MasterTracking). This is complete enough for an agent to use the tool correctly without needing additional context from siblings or external documentation.

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

Parameters5/5

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

The input schema is minimal (action and args), but the description fully compensates by defining both actions' required parameter 'tracking_id' as a mandatory UUID string. It also embeds the full tracking schema, giving meaning to the generic 'args' field. This is a complete parameter description beyond the structured 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 immediately states the tool's function: 'Operations on tracking objects' and specifies 'read or poll tracking status by tracking ID (UUID).' It clearly distinguishes between the two sub-actions ('read' for virtual service operations, 'read_asset_tracking' for asset uploads), making it easy to select the correct action.

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

Usage Guidelines5/5

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

The description provides explicit guidance: 'Call this whenever you have a tracking ID and need to know the status or result of an async operation.' It also warns against using 'read' for asset tracking, directing users to 'read_asset_tracking' instead. This goes beyond simple context and gives clear when-to-use instructions.

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/Blazemeter/sv-mcp'

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