Skip to main content
Glama
Joy MCP Server

Joy MCP Server

Official

joy_read

Read the current Joy page to extract text and numbered buttons, links, and fields, or limit the read to a specific element.

Instructions

Read the current Joy 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": "joy_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load. "Read" plus the content enumeration makes the read-only, inspection nature clear, but it leaves open whether element numbering is stable across reads, whether output is truncated on large pages, and whether it has side effects on the page's focus/state.

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 scope, with no filler. The enumeration of returned content earns its place by telling the agent what it can expect to work with.

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 and no annotations, the description covers purpose and returned content adequately. Minor gaps remain around element numbering semantics and result size, but nothing blocks correct invocation.

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 there, so the baseline applies. The phrase "Read only inside this element" restates the schema's own wording rather than adding new meaning such as what index space the number lives in or what happens if the element is unknown.

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?

Uses a specific verb ("Read") on a specific resource ("the current Joy page") and enumerates the returned content: text, numbered buttons, links, and fields. It is distinguishable from action siblings like joy_click and joy_type, though it never names them explicitly.

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?

Usage is implied — you read a page to see its content and the numbered elements you can act on — but the description never states when to call this versus joy_status, nor does it say to read before clicking or typing. No exclusions or prerequisites are given.

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