Skip to main content
Glama

get_requests

Read-only

Read change requests users send from the Tether popup, including reference images, for the shared tab so agents can handle open requests and resolve them.

Instructions

Read change requests the user sent from the Tether popup: what they want changed on a site, often with reference images (screenshots, mockups, mood boards). The tab they sent it from is shared with you. Handle open requests, then call resolve_request.

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_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
statusNoDefault open.

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 only cover readOnlyHint, and the description goes beyond that by disclosing that requests often carry reference images and that the originating tab is shared with the agent — useful context for interpreting results. It says nothing about result size, ordering, or what happens with already-resolved requests, which limits it to a 4.

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?

Three short sentences, front-loaded with the core purpose and ending with the required follow-up call. The word 'Handle' is slightly vague, but nothing is padded or redundant.

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 two-parameter read tool with no output schema, the description covers what is returned (change requests plus images), the tab context, and the next step. The only real gap is the unlabeled id filter and the absence of any note on result volume or pagination.

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 description coverage sits at 50%: status is documented with its default, but no parameters are explained in the description at all. The undocumented id parameter is not compensated for, so the description adds no meaning beyond the schema.

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 uses a specific verb and resource ('Read change requests the user sent from the Tether popup') and explains what a change request actually is — a site change with reference images. That domain framing separates it from generic reads like read_text or console_messages. It stops short of an explicit contrast with other read tools, which keeps it below a 5.

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

Usage Guidelines4/5

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

It gives a concrete workflow rule: 'Handle open requests, then call resolve_request,' which tells the agent both when to call this tool and what should follow. It doesn't state exclusions or when not to fetch requests, so it isn't a full when/when-not treatment.

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