Skip to main content
Glama
Blazemeter

BlazeMeter Service Virtualization MCP Server

Official
by Blazemeter

virtual_services_asset

Manage assets like certificates, keys, and keystores for service virtualization. Upload new asset files, list, read asset details, and set keystore passwords.

Instructions

    Operations on assets. 
    Use this when a user needs to create an asset from file. Supported file extensions: .jks, .keystore, .key, .crt, 
    .cer, .p7b, .p7c, .p7s, .pem
    Actions:
    - read: Reads an Asset. Get the information of an asset.
        args(dict): Dictionary with the following required parameters:
            workspace_id (int): Mandatory. The id of the workspace to list asset from.
            asset_id (int): Mandatory. The id of the asset.
    - list: List all assets. 
        args(dict): Dictionary with the following required parameters:
            workspace_id (int): Mandatory. The id of the workspace to list services from.
            limit (int, default=10, valid=[1 to 50]): The number of assets to list.
            offset (int, default=0): Number of assets to skip.
    - set_keystore_passwords: Sets keystore password for the keystore asset.
        args(dict): Dictionary with the following required parameters:
            workspace_id (int): Mandatory. The id of the workspace to list asset from.
            asset_id (int): Mandatory. The id of the asset.
            keystore_password (str): Optional. The keystore password.
            key_passwords (dict): Optional. The dictionary of key alias x password.
    - upload: Create a new asset from file.
        Action result contains tracking id to track the create asset process. Use tracking tool to track it.
        Creation of the asset is finished, when tracking status is 'FINISHED'. If creation fails, tracking status is 'FAILED'.
        args(dict): Dictionary with the following required parameters:
            workspace_id (int): Mandatory. The id of the workspace to store the asset.
            file_path (int): Mandatory. The full file path to the file for upload.
    Asset Schema:
    {'properties': {'id': {'description': 'The unique identifier of the asset', 'title': 'Id', 'type': 'integer'}, 'name': {'description': 'The name of the asset', 'title': 'Name', 'type': 'string'}, 'type': {'description': 'The type of the asset', 'title': 'Type', 'type': 'string'}, 'primaryMetadata': {'anyOf': [{'additionalProperties': True, 'type': 'object'}, {'type': 'null'}], 'default': None, 'description': 'The asset metadata', 'title': 'Primarymetadata'}}, 'required': ['id', 'name', 'type'], 'title': 'Asset', 'type': 'object'}
    Asset create action result schema:
    {'properties': {'tracking_id': {'description': 'Action tracking id', 'title': 'Tracking Id', 'type': 'string'}}, 'required': ['tracking_id'], 'title': 'ActionResult', '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
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It adds valuable behavioral context: upload returns a tracking id and the process completes when tracking status is 'FINISHED' or 'FAILED'. It also lists supported file extensions and provides output schemas. However, it doesn't disclose permissions, reversibility, or side effects for mutation actions like set_keystore_passwords, leaving some behavioral gaps.

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

Conciseness3/5

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

The description is well-structured with action headers and clear formatting, but it's lengthy. The Asset Schema and ActionResult schema are redundant with the provided output schema, adding bloat without new information. The core action documentation is concise, but overall could be trimmed.

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

Completeness4/5

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

The description covers all four actions, all parameters, file extensions, and the tracking process, making it largely complete for a complex multi-action tool. It falls short on error handling and authorization details, but the provided schemas and per-action docs cover most agent needs.

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 generic (action + args) with 0% coverage, so the description is the sole source of parameter semantics. It thoroughly documents each action's args, including types, mandatory/optional status, defaults (limit=10, offset=0), and valid ranges (1-50). This fully compensates for the minimal schema.

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 'Operations on assets' and lists four distinct actions (read, list, set_keystore_passwords, upload), making the resource and verbs specific. However, the initial 'Use this when' focuses only on creating from file, which slightly conflicts with the broader read/list actions, so not a perfect 5.

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

Usage Guidelines4/5

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

It explicitly says 'Use this when a user needs to create an asset from file' and lists supported file extensions as prerequisites. The upload action also advises using the tracking tool, providing an alternative. However, it doesn't explicitly say when not to use other sibling tools, but the resource-specific naming helps.

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