Skip to main content
Glama
Sign In
Weezevent MCP Server

Weezevent MCP Server

by cotlet-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

weezevent_read

Reads the current Weezevent page, including visible text and numbered buttons, links, and fields, to inspect event or account screens before choosing an action.

Instructions

Read the current Weezevent page: its text and numbered buttons, links and fields.

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

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description must carry the behavioral burden. It usefully discloses the shape of the return (text, numbered buttons, links, fields), which is real value, but says nothing about read-only/non-mutating nature, snapshot freshness, truncation of long pages, or what happens when no page is open.

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?

One front-loaded sentence with no filler; the resource comes first and the payload list follows. It is arguably too terse rather than padded, but every clause earns its place.

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?

For a simple one-optional-parameter read tool with no output schema, describing the returned content (text, numbered buttons, links, fields) is close to sufficient. The remaining gap is the interaction between the 'element' scoping parameter and normal full-page reads.

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 coverage is 100% and the single optional 'element' parameter is documented in the schema as 'Read only inside this element.' The description adds nothing about scoping to an element or about how the numeric index relates to the returned numbering, so baseline 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 and resource ("Read the current Weezevent page") and enumerates what comes back: text, numbered buttons, links, fields. That distinguishes it from weezevent_click/type/open/close without naming them, though no sibling is called out explicitly.

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: 'current page' and 'numbered buttons' hint that this is the inspection step performed before clicking or typing, but the description never says when to use it versus weezevent_status or weezevent_guide, nor any precondition such as a page being open.

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