Skip to main content
Glama
Sign In
Genio520 ISP MCP

Genio520 ISP MCP

by eric612
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_target_info

Read-only

Reads Genio Android target device info: ABI, build details, and ADB connection status. Inspect this before building or deploying to confirm the device and diagnose ADB issues without changing system state.

Instructions

Read Genio Android/ABI/build and ADB status. No system changes.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and 'No system changes' merely restates that guarantee. It adds no further behavioral context such as whether ADB must be running, failure modes, or how quickly state is refreshed.

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?

Two terse sentences with the verb and scope front-loaded and the safety constraint in the trailing position. No wasted text.

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?

With no output schema, the description usefully enumerates the dimensions returned (Android/ABI/build plus ADB status). Only the lack of any note on output shape or ADB prerequisites keeps it short of full completeness.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool 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?

Uses a specific verb (Read) with a concrete set of resources: Genio Android/ABI/build state and ADB status. It is distinguishable from the camera- and source-file-oriented siblings, though the niche term 'Genio' is left unexplained.

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 read-only framing implies the tool is used to inspect target/environment state before other operations, but no explicit when-to-use, prerequisites, or alternatives among the siblings are named.

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