Joist MCP

joist_read

Read the current Joist page to capture its text and numbered buttons, links, and fields, optionally limited to one element.

Instructions

Read the current Joist 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": "joist_read"
  }
}

Input Schema

Name	Required	Description	Default
`element`	No	Read only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 13, 2026

TDQS

B3.4/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 disclosure burden. It usefully discloses that elements come back numbered (presumably for referencing by index in joist_click/joist_type), which is real behavioral context, but it says nothing about pagination, truncation of large pages, error behavior when no page is open, or whether reading has side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

A single compact sentence that front-loads the verb and resource and then lists the returned content types. Very little waste, though it could be marginally tightened and one clause about page state would help rather than hurt.

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?

For a one-parameter read tool with no output schema and no annotations, the description covers what content is returned but not how it is structured or numbered, nor what happens on an empty or unopened page. It is adequate to attempt the call but leaves meaningful gaps an agent may have to discover by trial.

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 as 'Read only inside this element.' The description adds no further meaning, such as whether the integer is an element index from a prior read or a DOM id, and does not explain behavior when it is omitted. Baseline 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?

States a specific verb and resource: reads the current Joist page, and enumerates what is returned (text, numbered buttons, links, fields). This clearly distinguishes it from sibling tools like joist_click, joist_type, joist_open; it only lacks explicit naming of those alternatives.

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 phrase 'current Joist page' implies this tool inspects whatever page is already open, so an agent can infer it is a pre-action inspection step before clicking or typing. There is no explicit when-to-use statement, no exclusion of alternatives, and no mention of joist_open for navigating first.

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

Deploy Server