Skip to main content
Glama
Blazemeter

BlazeMeter Service Virtualization MCP Server

Official
by Blazemeter

virtual_services_configuration

Manage virtual service configurations by creating, reading, listing, and updating them in a workspace.

Instructions

    Operations on virtual service configurations. 
    Use this when a user needs to create or update a virtual service configuration.
    Actions:
    - read: Read a Configuration.
        args(dict): Dictionary with the following required parameters:
            workspace_id (int): Mandatory. The id of the workspace to list configurations from.
            configuration_id (int): Mandatory. The id of the configuration to get information.
    - list: List all configurations. 
        args(dict): Dictionary with the following required parameters:
            workspace_id (int): Mandatory. The id of the workspace to list configurations from.
            limit (int, default=10, valid=[1 to 50]): The number of configurations to list.
            offset (int, default=0): Number of configurations to skip.
    - create: Create a new configuration.
        args(dict): Dictionary with the following required parameters:
            workspace_id (int): Mandatory. The ID of the workspace in which to create the configuration.
            configuration_name (str): Mandatory. The name of the configuration to create.
            configuration_map (Dict[str, str]): Mandatory. A map of configuration parameters and their corresponding values.
    - update: Update an existing configuration.
        args(dict): Dictionary with the following required parameters:
            workspace_id (int): Mandatory. The ID of the workspace containing the configuration.
            configuration_id (int): Mandatory. The ID of the configuration to update.
            configuration_name (str): Mandatory. The new or updated name of the configuration.
            configuration_map (Dict[str, str]): Mandatory. A map of configuration parameters and their corresponding values.
    Configuration Schema:
    {'additionalProperties': True, 'properties': {'id': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'default': None, 'description': 'Configuration id', 'title': 'Id'}, 'name': {'description': 'Configuration parameter name', 'title': 'Name', 'type': 'string'}, 'description': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'default': None, 'description': 'Configuration parameter name', 'title': 'Description'}, 'configurationMap': {'anyOf': [{'additionalProperties': {'type': 'string'}, 'type': 'object'}, {'type': 'null'}], 'description': 'Configuration map', 'title': 'Configurationmap'}}, 'required': ['name', 'configurationMap'], 'title': 'Configuration', '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?

With no annotations, the description carries the full burden. It discloses the four actions and their parameters, but omits important behavior such as whether updates are full replacements or merges, and possible side effects like overwriting existing configurations. This leaves moderate ambiguity.

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 lengthy but well-organized by action. The embedded Configuration Schema is redundant given the likely output schema, but does not detract significantly. Overall, it earns its length through thorough coverage of the tool's complexity.

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 four-action tool with nested arguments, this is nearly complete, documenting all necessary parameters and providing a data schema. It falls short only in not explaining behavioral outcomes (e.g., error conditions), but is still highly actionable.

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 just a generic 'action/args' envelope, but the description details every required parameter per action, including types, mandatory flags, and defaults for limit/offset. This greatly exceeds the schema and gives the agent precise invocation guidance.

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 opens with 'Operations on virtual service configurations' and enumerates four explicit actions (read, list, create, update), clearly identifying the tool's scope and distinguishing it from sibling tools focused on other virtual service resources.

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 states 'Use this when a user needs to create or update a virtual service configuration,' giving a direct usage trigger. It doesn't mention alternatives, but the tool's config-specific scope makes the guidance sufficient for selecting it over siblings.

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