Skip to main content
Glama
Blazemeter

BlazeMeter Service Virtualization MCP Server

Official
by Blazemeter

virtual_services_action

Create, read, list, and assign certificates or keystores to actions within virtual service transactions.

Instructions

    Operations on actions. 
    Use this when a user needs to create, read or list actions for a transaction.
    Actions:
    - read: Reads a single action of a transaction with full details.
        args(dict):
            workspace_id (int): Mandatory. The id of the workspace.
            transaction_id (int): Mandatory. The id of the transaction.
            action_id (int): Mandatory. The id of the action to read.
    - list: Lists all actions of a transaction (minimal info).
        args(dict):
            workspace_id (int): Mandatory. The id of the workspace.
            transaction_id (int): Mandatory. The id of the transaction.
            sort (str): Optional. Field to sort the actions by.
    - create_http_call: Creates an http call action for transaction. This action is executed synchronously.
        args(dict): Dictionary with the following required parameters:
            action_name (str): Mandatory. The name of the action.
            workspace_id (int): Mandatory. The id of the workspace to list services from.
            transaction_id (int): Mandatory. The id of the transaction.
            action (WebAction): Mandatory. The action definition. See WebAction schema below.
    - create_web_hook: Creates a web hook action for transaction. This action is executed asynchronously.
        args(dict): Dictionary with the following required parameters:
            action_name (str): Mandatory. The name of the action.
            workspace_id (int): Mandatory. The id of the workspace to list services from.
            transaction_id (int): Mandatory. The id of the transaction.
            action (WebAction): Mandatory. The action definition. See WebAction schema below.
    - assign_keystore: Assign keystore asset to the action.
        args(dict):
            id (int): Mandatory. The id of the action.
            transaction_id (int): Mandatory. The id of the transaction.
            asset_id (int): Mandatory. The id of the keystore asset to assign.
            alias (str): Mandatory. The certificate alias to use.
            workspace_id (int): Mandatory. The id of the workspace.  
    - assign_certificate: Assign certificate asset to the action.
        args(dict):
            id (int): Mandatory. The id of the action.
            transaction_id (int): Mandatory. The id of the transaction.
            asset_id (int): Mandatory. The id of the certificate asset to assign.
            workspace_id (int): Mandatory. The id of the workspace.                      
    Action Schema:
    {'$defs': {'HttpHeader': {'additionalProperties': True, 'properties': {'name': {'description': 'HTTP header name', 'title': 'Name', 'type': 'string'}, 'value': {'description': 'HTTP header value', 'title': 'Value', 'type': 'string'}}, 'required': ['name', 'value'], 'title': 'HttpHeader', 'type': 'object'}, 'QueryParameter': {'additionalProperties': True, 'properties': {'name': {'description': 'Query parameter name', 'title': 'Name', 'type': 'string'}, 'value': {'description': 'Query parameter value', 'title': 'Value', 'type': 'string'}}, 'required': ['name', 'value'], 'title': 'QueryParameter', 'type': 'object'}}, 'properties': {'urlValue': {'description': 'Action request url value', 'title': 'Urlvalue', 'type': 'string'}, 'urlMethod': {'description': "Action request HTTP method of the request for the transaction request matching. Uppercase, e.g., 'GET', 'POST'", 'title': 'Urlmethod', 'type': 'string'}, 'bodyContent': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'description': 'Action request body content', 'title': 'Bodycontent'}, 'queryParameters': {'anyOf': [{'items': {'$ref': '#/$defs/QueryParameter'}, 'type': 'array'}, {'type': 'null'}], 'default': [], 'description': 'List of query parameters', 'title': 'Queryparameters'}, 'headers': {'anyOf': [{'items': {'$ref': '#/$defs/HttpHeader'}, 'type': 'array'}, {'type': 'null'}], 'default': [], 'description': 'List of response headers', 'title': 'Headers'}}, 'required': ['urlValue', 'urlMethod', 'bodyContent'], 'title': 'WebAction', '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
Behavior4/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does well by noting synchronous execution for create_http_call, asynchronous for create_web_hook, and distinguishing 'full details' (read) from 'minimal info' (list). It also clarifies the 'assign' operations target keystore/certificate assets. However, it does not explicitly mention side effects, error behavior, or permissions, which would be useful for a mutation-heavy tool.

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?

The description is long but well-structured with a clear hierarchy: top-level purpose, then sub-operations each with their own args. It uses bullet-like formatting with consistent parameter listings. Every sentence serves a purpose, but the abundance of detail makes it somewhat dense. Front-loaded with the core purpose and usage statement.

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?

For a multi-operation tool with no annotations, the description provides substantial context: operation semantics, parameter meanings, and even the WebAction schema. It distinguishes synchronous vs asynchronous behavior and read vs list detail levels. The presence of an output schema reduces the need to document return values. Minor gaps include lack of error handling or response format details, but overall it's complete enough for an agent to select and invoke correctly.

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?

Schema description coverage is 0%, so the description must fully compensate. It does so comprehensively: each sub-action lists every parameter with mandatory/optional status and a clear description. The embedded WebAction schema provides nested object structure with types, defaults, and field descriptions. This far exceeds the minimal input schema and gives the agent everything needed to construct valid arguments.

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 it handles 'Operations on actions' and specifies 'Use this when a user needs to create, read or list actions for a transaction.' This is a specific verb+resource combination that distinguishes it from sibling tools focused on services, transactions, or assets. The sub-operations are enumerated, making the scope unambiguous.

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 states when to use the tool: 'Use this when a user needs to create, read or list actions for a transaction.' While it doesn't name alternative tools or provide exclusions, the context of sibling tools and the clear resource focus (actions within transactions) gives sufficient guidance. No misinformation or ambiguity.

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