Skip to main content
Glama

List Swift Evolution proposals

apple_swift_evolution_list
Read-onlyIdempotent

Lists Swift Evolution proposals with optional status filters (Implemented, Accepted, Rejected, Active review) to help track language changes.

Instructions

List proposals (optionally filter by status: Implemented, Accepted, Rejected, Active review).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
formatNoResponse formatmarkdown
offsetNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / offset / maximum
      Added value: +9007199254740991
  2. First observedv0.2.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description's contribution is the enumerated status values, which go beyond the annotations, but it says nothing about pagination behavior, default page size, or response shape for a tool that supports limit/offset.

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 tight sentence with the core action front-loaded and the modifier in parentheses; no filler or redundancy. It is arguably too terse rather than too long, but on structure and economy it is clean.

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?

For a simple four-parameter list tool with no output schema, the description covers the main action and the filter vocabulary. It omits pagination guidance and the markdown/json format default, so an agent would still need to open the schema to call it well.

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 coverage is only 25% (only "format" is documented), so the description must compensate. It does supply the otherwise missing status vocabulary (Implemented, Accepted, Rejected, Active review) for an untyped string parameter, which is genuine added value, but limit and offset semantics (pagination, max 100) remain undocumented in both places.

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?

States a specific verb and resource ("List proposals") plus the available status filter values, so an agent knows exactly what the tool returns. It does not distinguish itself from the sibling apple_swift_evolution_filter, which likely offers overlapping filtering, leaving the boundary implicit.

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 parenthetical "optionally filter by status" implies the intended usage pattern (browse, narrow if needed) and enumerates valid filter values. However, there is no explicit when-to-use versus apple_swift_evolution_filter or apple_swift_evolution_get, and no exclusions, so routing between the three evolution tools is left to inference.

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