Skip to main content
Glama

List Architectures

list_architectures
Idempotent

Lists thin or universal Mach-O slices with offsets, sizes, alignment, explicit coverage, and native-tool provenance to inspect binary architectures.

Instructions

List thin or universal Mach-O slices with offsets, sizes, alignment, explicit coverage, and native-tool provenance.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_architectures"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare the safety profile (not read-only, open-world, idempotent, non-destructive). The description adds genuinely useful context beyond them: the returned fields and the phrase 'native-tool provenance', which hints that external native tooling is invoked and explains the openWorldHint. It still does not say which binary is inspected or whether results are cached, so the addition is partial.

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?

A single front-loaded sentence with no filler, and the resource is named before the field list. It is dense, though the trailing field enumeration reads as a compressed feature dump rather than guiding the agent's decision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters and no output schema, the description does the right thing by describing the return shape. However, a zero-parameter tool is ambiguous about scope: it never says which binary, session, or session-wide context the slices are read from, which is the one fact an agent needs before invoking it.

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 no parameter semantics to document and the baseline of 4 applies. The description's enumeration of offsets, sizes, alignment, and coverage correctly describes output rather than input.

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 ('List') plus a precise resource ('thin or universal Mach-O slices') and enumerates what each entry carries: offsets, sizes, alignment, coverage, provenance. This is far more specific than a tautology, but it never contrasts itself with related listing siblings such as list_segments or binary_overview, so an agent must infer the boundary.

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 statement of when to call this versus alternatives, no prerequisite (e.g. that a binary must already be loaded or a session opened), and no exclusion. The reader is left to infer the trigger condition entirely from the noun phrase 'Mach-O slices'.

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