Skip to main content
Glama

whova_read

Read the current Whova page to capture its text and numbered buttons, links, and fields, optionally scoped to one element for targeted inspection.

Instructions

Read the current Whova 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": "whova_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the whole burden, and it does disclose the substance of the response: page text plus numbered buttons, links, and fields, which is the key behavior an agent needs. It omits whether the read is non-destructive, how large the output may be, or whether the snapshot goes stale after actions.

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?

A single front-loaded sentence with the scope first and the returned artifacts listed after the colon. No filler, nothing repeated, and the punctuation carries the structure.

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 one-parameter read with no output schema and no annotations, the description covers both scope (current page only) and return shape, which is what an agent needs to invoke it. The remaining gap is operational: no guidance on using the returned element numbers with the click/type siblings, and no note on snapshot freshness.

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 element parameter is already documented as "Read only inside this element," so the schema does the work. The mention of "numbered buttons" hints at how elements are indexed, but the description never explains how the element value relates to those numbers, so it adds little beyond the schema.

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?

Names a specific verb and resource ("Read the current Whova page") and enumerates what the read returns: text, numbered buttons, links, fields. That vocabulary ties it implicitly to the click/type siblings, but it never names an alternative or states an explicit contrast with whova_click or whova_open, so it stops short of the top band.

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?

The verb "Read" implies this is the inspection step, but the description never says when to call it, whether it should precede whova_click/whova_type, or whether re-reading is needed after an action. Usage is inferable from the operation name rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.