Skip to main content
Glama
manykarim

RobotMCP

by manykarim
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

analyze_scenario

Convert natural-language test scenarios into structured automation sessions. Detect context, configure libraries, and get a session ID for executing steps.

Instructions

Analyze a natural-language scenario into structured intent and create a session.

WORKFLOW: This is the single front door — your FIRST tool call for any test scenario. It CREATES the session, so do NOT also call manage_session(action="init") for the same scenario (that causes redundant session churn). Reuse the returned session_id in every later call.

What this tool does:

  1. Creates a new session with unique session_id (or reuses provided one)

  2. Analyzes scenario to detect context (web/api/mobile/desktop)

  3. Auto-configures libraries based on scenario text

  4. Returns session_id for use in ALL subsequent tool calls

CRITICAL: Save the session_id from the response and use it in all other tool calls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contextNoApplication context (e.g., "web", "mobile", "api", "desktop"); defaults to "web". An explicit context="desktop" DETERMINISTICALLY forces a native desktop (PlatynUI) session regardless of scenario wording — phrasing or word order cannot flip it to mobile/Appium. Use it for Linux/GNOME desktop GUI scenarios.web
scenarioYesHuman-language description of the task to automate.
session_idNoOptional existing session id to reuse; if omitted, a new one is created.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It details session creation, context detection, library auto-configuration, and session_id reuse. However, it does not mention error conditions or rate limits.

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?

Well-structured with headings and bullet points, but slightly lengthy. Every sentence contributes meaning, though some rephrasing could reduce verbosity.

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?

Given the presence of an output schema, the description covers the essential workflow, session reuse, and deterministic context handling. It could be improved by mentioning error handling or prerequisites.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

100% schema coverage means parameters are documented. The description adds value by explaining the deterministic behavior of context parameter (e.g., context='desktop' forces PlatynUI) and optional session_id reuse.

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 is the 'single front door' tool for any test scenario, creating a session and analyzing scenario into structured intent. It explicitly distinguishes from manage_session by warning not to call both.

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

Usage Guidelines5/5

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

Provides explicit workflow: 'FIRST tool call for any test scenario' and advises against redundant manage_session calls. Also explains when to reuse session_id.

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/manykarim/rf-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server