Skip to main content
Glama
Sign In
mcp-appium

mcp-appium

by julien-becheny
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_session_info

Retrieve current Appium session details including platform, capabilities, and screen size to inspect live session state.

Instructions

Retourne les informations de la session Appium en cours : plateforme, capabilities, taille d'écran, etc.

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": "get_session_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/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. The verb 'Retourne' implies a read-only operation, and 'session en cours' suggests an active session is required, but it does not explicitly state that there are no side effects or what happens if no session exists. Basic behavioral context is present but not deeply disclosed.

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, short sentence that immediately states the tool's action and provides illustrative examples. It is concise, front-loaded, and contains no filler.

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?

This is a simple tool with no parameters and an output schema, so the description does not need to explain return formats or parameters. It sufficiently states what the tool returns and implies the active-session context. It could be more explicit about the precondition of an active session, but overall it is complete for the tool's complexity.

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?

The tool has zero parameters and the schema reflects that, so there are no parameter semantics to document. The description does not need to add anything about parameters. Baseline of 4 for 0-parameter tools applies.

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 the tool 'Retourne les informations de la session Appium en cours' and lists examples (platform, capabilities, screen size). This makes the specific resource and action clear, and it is distinct from sibling tools like get_page_source or get_element_info.

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 gives no guidance on when to use this tool versus alternatives. It does not mention comparisons, prerequisites, or exclusions. An agent must infer from the tool name and examples that this is for retrieving session details.

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