Skip to main content
Glama
Sign In
Eversports Studio Manager MCP Server

Eversports Studio Manager MCP Server

by cotlet-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

eversports_studio_manager_click

Clicks a numbered element on the current Eversports Studio Manager page to navigate or act on studio settings, using the element number from the last read.

Instructions

Click a numbered element on the current Eversports Studio Manager page.

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": {
      "element": "<element>"
    },
    "name": "eversports_studio_manager_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.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 behavioral burden. It does not disclose what a click does beyond the act itself: whether it navigates, submits, mutates state, waits for load, invalidates previously read element numbers, or what error occurs for an out-of-range element.

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?

A single front-loaded sentence with zero filler. It is efficient, though the space saved could have been used to state the read-before-click prerequisite.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an action tool with no annotations and no output schema, the description should explain the prerequisite read step and the post-click effect. Neither is covered, leaving an agent without enough information to sequence or interpret the call safely.

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 single parameter already carries the meaning 'Element number from the last read.' The description adds the word 'numbered' but nothing about indexing source or staleness beyond what the schema states, so the baseline of 3 applies.

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?

States a specific verb (click) and a specific target (a numbered element on the current Eversports Studio Manager page), which distinguishes it from siblings like read, type, open, and close. It stops short of explicitly naming those siblings or stating the relationship to them.

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

Usage Guidelines3/5

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

Usage is only implied: 'numbered element' and the schema note 'Element number from the last read' hint that a read must precede a click, but the description never states this prerequisite or says when to prefer type/open/close instead. No when-not guidance exists.

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