Skip to main content
Glama

get_requests

Fetch recent HTTP requests from a Mac or iOS Simulator app, newest first, to inspect methods, URLs, statuses, errors, timing, and optional bodies for network debugging.

Instructions

A simulator app's recent HTTP requests, newest first: method, URL, status, errors, time, and optionally bodies. Needs the app to have been launched with request monitoring (relaunch_app).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "app": "<app>",
      "simulator": "<simulator>"
    },
    "name": "get_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYesThe app: a bundle ID like com.me.MyApp, an app name, or * for every app in a simulator.
limitNoHow many, 1 to 500. Default 50.
filterNoA search: words, or filters like status:4xx, method:POST, host:api, path:/v1, is:failed, -host:cdn.
simulatorYesFor iOS Simulator apps: booted, any, a device name or a UDID. Leave out for a Mac app.
include_bodiesNoInclude request and response bodies (up to 4,000 characters each).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does disclose two non-obvious traits: result ordering (newest first) and the monitoring prerequisite that gates whether any data exists. It does not say what happens when monitoring was never enabled (empty result vs. error) or how fresh/session-scoped the data is, leaving meaningful gaps.

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 dense sentences: the first gives the resource, ordering, and payload; the second gives the prerequisite and the tool that resolves it. No filler or redundancy.

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 read tool with five fully documented parameters and no output schema, the description usefully substitutes for a return-value spec by listing the fields returned. The remaining gap is error/empty-state behavior when monitoring is off, which matters for a tool whose entire output depends on that condition.

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 is 100%, so every parameter including app, simulator, limit, filter, and include_bodies is already documented in the schema. The description only echoes 'optionally bodies' and adds no syntax or format guidance beyond what the schema provides, which is the baseline case.

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 names a concrete resource ('A simulator app's recent HTTP requests, newest first') and enumerates the returned fields (method, URL, status, errors, time, bodies), so an agent knows exactly what it gets. It does not explicitly contrast itself with sibling tools such as status or list_targets, which keeps it short of 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 states a hard precondition for effective use: the app must have been launched with request monitoring, and it names relaunch_app as the way to satisfy that. There is no explicit when-not guidance or mention of alternatives for other request-related needs, so it stops short of a 5.

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