Skip to main content
Glama
Sign In
moreplay

moreplay

by JastinXyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

observe

Read-only

Reads the current Android screen as one line per UI element with refs, labels, IDs, coordinates, and flags for precise targeting in subsequent actions.

Instructions

Current screen as one line per element: @ref Class "label" #id [x,y] flags. Use refs/text/id from here in act.

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": "observe"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds meaningful behavioral detail by disclosing the output line format and fields (ref, class, label, id, coordinates, flags), though it does not mention freshness, pagination, or snapshot limitations.

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?

The description is a single front-loaded sentence followed by a compact format template. Every phrase contributes either the return shape or the downstream usage instruction.

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?

There is no output schema, so the description must convey the return shape itself, and it does so with the exact one-line-per-element format. For a zero-parameter read-only tool this is largely complete, though freshness or scope details are absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the baseline score of 4 applies. The description correctly says nothing about parameters and instead focuses on the output format.

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 states a specific resource and output shape: the current screen as one line per element, with an exact line format. It distinguishes itself from act by saying the refs/text/id should be used there, though it does not explicitly contrast with screenshot or flow.

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?

It says to use refs/text/id from here in `act`, which implies observing before acting, but it gives no explicit when-to-use versus screenshot or flow and no when-not-to-use guidance.

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

Deploy Server

Other Tools