Skip to main content
Glama
Sign In
lyzr-mcp

lyzr-mcp

by nandanNM
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List World Model Scenarios

lyzr_world_model_list_scenarios
Read-onlyIdempotent

List all scenarios associated with a given world model ID. Get a clear overview of defined scenarios to manage or analyze world model behavior.

Instructions

List the scenarios defined on a world model.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "world_model_id": "<world_model_id>"
    },
    "name": "lyzr_world_model_list_scenarios"
  }
}

Input Schema

NameRequiredDescriptionDefault
world_model_idYesThe world model id

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?

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description does not contradict them. However, it adds no additional behavioral context beyond what annotations imply (e.g., return format, error behavior, or whether the world model must exist). The description is consistent but minimally informative.

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, concise sentence that contains no extraneous words. It is appropriately front-loaded, stating the verb and resource directly.

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 tool is simple (1 parameter, no output schema) and annotations are strong, but the description still lacks detail about return values, pagination, or ordering of scenarios. It is adequate but leaves clear gaps, especially since no output schema exists.

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?

Schema description coverage is 100% and the parameter 'world_model_id' is documented as 'The world model id'. The tool description adds no further semantic meaning beyond the schema, so the baseline score of 3 is appropriate.

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 ('List') and the resource ('scenarios defined on a world model'), making the purpose unambiguous. However, it does not explicitly differentiate from sibling list tools like lyzr_world_model_list_personas, though the resource type is specific enough.

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 vs alternatives, no prerequisites, and no context. It is a bare statement of functionality with no 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