Skip to main content
Glama

accelo_read

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

Instructions

Read the current Accelo 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": "accelo_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses what the response contains (text, numbered buttons, links, fields), which is genuinely useful, but says nothing about whether the call mutates state (implied no), whether it scrolls or advances the page, or how the numbering relates to element indices.

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?

One sentence, front-loaded with the verb and target, and each listed item (text, buttons, links, fields) adds distinct information. Nothing is wasted.

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 single-optional-parameter read tool with no output schema, the description is nearly sufficient: it tells the agent what comes back and implies a safe observation step. The main gap is the unexplained relationship between the 'numbered' elements and the optional element index used to scope the read.

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, so the baseline of 3 applies. The description adds no information about how the element index relates to the 'numbered' buttons/fields it mentions, which would have been a valuable bridge.

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?

The description names a specific verb ('Read') and resource ('the current Accelo page') and enumerates what is returned: text, numbered buttons, links and fields. That clearly separates it from siblings like accelo_click or accelo_type, though it does not explicitly contrast with accelo_status or accelo_guide.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no alternative is named. At best, the word 'current' and the read framing imply 'inspect before acting', but the agent must infer this entirely.

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