Skip to main content
Glama

Get Objc Classes

get_objc_classes
Idempotent

Discover and deduplicate Objective-C class labels, with optional filtering by literal substring or pattern to isolate matching classes.

Instructions

Discover and deduplicate Objective-C class labels, optionally filtering by literal substring.

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": {
      "pattern": ""
    },
    "name": "get_objc_classes"
  }
}

Input Schema

NameRequiredDescriptionDefault
patternNoLiteral text or regular expression used to filter matching results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The description discloses a non-obvious behavioral trait — results are deduplicated — and that filtering is literal substring matching. Annotations already cover the safety profile (idempotent, non-destructive, closed-world), though readOnlyHint=false is odd for a lookup tool and the description neither confirms nor contradicts it. It says nothing about scope (whole binary vs. session) or result ordering.

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 no filler. It is arguably too terse rather than bloated.

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 one-optional-param read-style lookup with no output schema, the description is minimally adequate but silent on return shape, scope, and prerequisites. Given the simplicity that is a modest gap, not a fatal one.

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 100% and the single optional param is fully documented, so baseline 3 applies. The description adds only that filtering is by "literal substring," which actually narrows the schema's stated support for regular expressions, so it contributes little new semantic value.

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?

Uses a specific verb pair ("discover and deduplicate") on a specific resource ("Objective-C class labels"), which tells an agent exactly what it returns. It does not explicitly differentiate itself from the sibling get_objc_protocols, leaving that distinction to the tool names.

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?

The word "optionally" implies the filter can be omitted, but there is no when-to-use guidance, no statement of when to prefer this over get_objc_protocols or search_android_classes, and no preconditions such as an open binary session.

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