Skip to main content
Glama

swift_galleries_read

Read the current Swift Galleries page to extract visible text and numbered buttons, links, and fields, with an option to scope results to a single element.

Instructions

Read the current Swift Galleries 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": "swift_galleries_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/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; "read" signals a non-mutating call, and disclosing that output is text plus numbered buttons/links/fields is genuinely useful behavioral detail. However it says nothing about output size or truncation, whether large pages are paged/limited, or whether the read has any side effects on page 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?

A single front-loaded sentence with zero filler; the resource comes first and the returned content types follow, which is exactly the order an agent needs. Nothing could be cut without losing information.

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?

The tool is simple (one optional integer, no nesting, no output schema), and the description covers what is read. With no output schema, though, it should say more about the shape of the returned listing and about the precondition that a page must be open, both of which the agent needs to call it correctly.

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 element parameter is already documented as "Read only inside this element." The description adds only indirect support, since calling out numbered buttons/links/fields is what makes element scoping meaningful; it adds no syntax, numbering basis, or default-scope detail beyond the schema.

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) plus the exact resource (the current Swift Galleries page) and enumerates what comes back: text, numbered buttons, links and fields. The word "current" implicitly scopes it against swift_galleries_open (navigate) and swift_galleries_click/type (act on what was read), so an agent can separate it from its siblings without opening a schema.

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 only implied: reading the current page presumes a page is already open, and the numbered elements are obviously meant to feed click/type. Neither of those dependencies nor any when-not condition (e.g. use swift_galleries_open to navigate first) is stated outright, so the agent must infer the workflow.

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