Skip to main content
Glama
Ashby MCP Server

Ashby MCP Server

ashby_read

Read the current Ashby page to capture its text plus numbered buttons, links, and fields, optionally scoped to a specific element.

Instructions

Read the current Ashby 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": "ashby_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the shape of the returned data (text plus numbered buttons, links, fields), which implies a read-only, non-mutating operation, and the 'numbered' indexing hints how click targets are referenced. It says nothing about size limits, truncation, pagination, 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?

One short sentence, front-loaded with the verb and resource, with the return contents packed in efficiently. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully characterizes the return value, and for a single optional parameter the surface area is small. However, the existence of ashby_open, ashby_close and ashby_status signals a page-state model that the description never addresses, leaving a real gap for a browser-driving tool.

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 fully documented there ('Read only inside this element'). The description adds no scoping or format detail beyond that, so the baseline of 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?

The description names a specific verb ('Read') and resource ('the current Ashby page') and enumerates what comes back: text, numbered buttons, links and fields. That is clearly distinct from the write-oriented siblings (ashby_click, ashby_type), though it does not explicitly name them.

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 statement of when to use this versus ashby_status, ashby_open or ashby_guide, and no prerequisites such as 'requires a page to be open first'. Usage is only loosely implied by the word 'current'.

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