Extract the visible text, numbered buttons, links, and fields from the current Meetup page, optionally limited to a single element, so an agent can inspect the page state before acting.
Read the current Meetup page: its text and numbered buttons, links and fields.
| Name | Required | Description | Default |
|---|---|---|---|
| element | No | Read only inside this element. |
Changes observed during successful MCP inspections.
v1.1.0Does 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 discloses the return shape superficially ('numbered buttons, links and fields') but says nothing about whether reads are live or snapshot, whether element numbering is stable across reads, cost/latency, or whether a read is a prerequisite for the indexed clicking tools.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One short sentence, front-loaded with the verb and target, then the returned content. No filler or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter read tool with a fully documented schema, the description covers the essentials. But with no annotations and no output schema, it should say more about the nature of the returned numbering and its interaction with the click/type siblings, which is the main thing an agent needs to call this correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with a single optional parameter already documented as 'Read only inside this element.' The description adds no meaning beyond that — it never explains what scoping to an element does to the returned numbering or why an agent would restrict the read.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Read') and resource ('the current Meetup page') and enumerates what is captured: text, numbered buttons, links and fields. This clearly separates it from the action siblings (meetup_click, meetup_type, meetup_open, meetup_close), though it never names them explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied — an agent infers it should call this to inspect page state before acting. There is no explicit when-to-use, when-not-to-use, or statement of the relationship to meetup_guide or meetup_status, which also sound like informational tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.