Skip to main content
Glama

Drisp

List Drisp devices

list_devices
Read-onlyIdempotent

The devices Drisp can put a screenshot on, each with the screenshot size in pixels that fills its screen exactly (portrait for phones, tablets and watches) and its page on drint.io.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already establish a safe, idempotent, closed-world read, and the description adds meaningful return-value context: each device has an exact screenshot pixel size and portrait orientation for phones, tablets and watches, plus a drint.io page. It does not mention ordering or pagination, but for a simple static list this is useful added context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that front-loads the resource and packs in size, orientation and source-page details without filler. It is grammatically dense and never states the 'list' action explicitly, which slightly reduces clarity.

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 zero-parameter, read-only list with no output schema, the description supplies the key return-value semantics: screenshot dimensions and the drint.io page. It leaves list ordering and completeness unstated, but the core information is present.

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 and an empty schema, so the baseline of 4 applies. There are no parameter semantics for the description to clarify.

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?

Identifies the resource as the set of devices Drisp can screenshot and describes what each entry carries: pixel size, portrait orientation for phones/tablets/watches, and a drint.io page. It never explicitly says 'list' and does not distinguish the tool from sibling device_mockup, so the verb and role must be inferred from the name and title.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use statement and no routing against the sibling device_mockup. An agent can infer this is a lookup for device metadata before taking a screenshot, but there are no stated conditions or exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.