Skip to main content
Glama
Sign In
crowd-test-mcp

crowd-test-mcp

by anhhuyn411-alt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

preview_mob

Preview the specific virtual user personas that will be generated for a given count and seed before initiating a crowd test.

Instructions

Preview the random mob members a given count/seed would generate.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "preview_mob"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNo
countNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/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 of disclosing behavior. It correctly implies a read-only preview operation, but it does not mention side effects, authentication needs, rate limits, or output format. More detail is needed for a complete behavioral picture.

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 a single, efficient sentence that directly states the tool's purpose without extraneous information. It is front-loaded and well-structured for quick understanding.

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?

The description is adequate given the presence of an output schema (not shown), which likely details return values. However, it omits information about default behaviors (e.g., what happens when seed is null) and does not clarify the relationship between count and seed. Overall, it is minimally sufficient but leaves gaps.

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?

With 0% schema description coverage, the description must compensate. It mentions 'count/seed', linking them to the parameters, but does not explain what seed controls (e.g., randomness source) or the meaning of count beyond quantity. It adds basic semantic value but lacks detail.

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 the action ('Preview') and the resource ('random mob members'), and mentions the key parameters (count/seed). It distinguishes the tool from siblings like 'list_personas' and 'read_report' by focusing on a specific preview of mob generation. However, it could be more explicit about what 'mob members' refers to.

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?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no scenarios where it should or should not be used. It is a minimal statement of function without usage context.

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

Deploy Server

Other Tools