Skip to main content
Glama

ptminder_read

Reads the current PTminder page, returning its text plus numbered buttons, links and fields so an agent can inspect on-screen elements before acting.

Instructions

Read the current PTminder 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": "ptminder_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/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 and does disclose the return shape (text plus numbered interactive elements), which is the key behavioral fact. It says nothing about large-page truncation, whether the element numbering is stable across reads, or whether reading has 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?

One sentence, front-loaded with the verb and resource, with the return contents in a compact clause. No filler, no repetition of the tool name.

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?

There is no output schema and no annotations, so the description is the only source of behavioral information, and it covers the essentials at a high level. For a page-scraping tool it is thin on what a large or complex page yields, which is the main thing an agent needs to plan around.

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 `element` parameter is already documented as "Read only inside this element" with a minimum of 1, so the baseline of 3 applies. The description's mention of numbered buttons/fields faintly implies what those numbers index, but it never connects that to the `element` argument.

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?

"Read the current PTminder page" names a specific verb and resource, and the colon-clause enumerates what comes back (text, numbered buttons, links, fields). That is enough to separate it from ptminder_click/ptminder_type without opening the schema, though it never explicitly contrasts itself with those siblings.

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 a page is the obvious prerequisite to acting on it, and the "numbered" detail hints the numbers are what other tools target. There is no explicit when-to-use, when-not, or named alternative, so the agent must infer the read-before-click workflow.

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