Skip to main content
Glama

evite_read

Reads the current Evite page text and numbered buttons, links, and fields, with an option to read only inside a specified element.

Instructions

Read the current Evite 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": "evite_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
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses the shape of the returned content (text, numbered buttons, links, fields), which is genuinely useful for a browser-read tool, but it never says whether reading alters page state, whether it waits for load, whether element numbering is stable across calls, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero filler; the verb and resource lead, and the returned content trails as a compact list. Nothing could be removed without losing information.

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?

The tool is simple (one optional parameter, no nesting) and the description covers the return content that a missing output schema would otherwise leave dark. Residual gaps are behavioral rather than structural: page-state effects and element-number stability are unstated, and there are no annotations to fill them in.

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 already documented in-schema as 'Read only inside this element.' The description adds no further meaning about scoping, indexing base, or behavior when the element is absent, so the baseline 3 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?

States a specific verb ('Read') against a specific resource ('the current Evite page') and enumerates what comes back: text plus numbered buttons, links and fields. The word 'current' implicitly separates it from evite_open, and 'read' separates it from evite_click/evite_type.

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?

Use is only implied: reading 'the current page' presupposes a page is already open, and the mention of 'numbered buttons' hints that numbers feed into evite_click. There is no explicit statement of when to call this versus evite_status or evite_guide, and no stated preconditions or exclusions.

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