Skip to main content
Glama

Get Objc Protocols

get_objc_protocols
Idempotent

Discover and deduplicate Objective-C and Swift protocol labels to resolve unique protocol references in reverse-engineering analysis.

Instructions

Discover and deduplicate Objective-C and Swift protocol labels.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and idempotentHint=true, which is an unusual profile for what reads as a discovery operation; the description neither explains nor resolves that tension. It also omits what "deduplicate" means operationally (same label across ObjC and Swift? across binaries?) and says nothing about what output or side effects to expect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single compact sentence with no wasted words, which is good, but the brevity comes at the cost of specification — the one clause present raises the undefined notion of deduplication without explaining it.

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 output schema and no parameters, the description is the only place to explain what comes back (a flat list of label strings? name/kind pairs?) and under what session conditions it works. It gestures at "labels" but leaves the return shape and scoping to inference, which is thin for a tool whose annotations are ambiguous.

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 nothing for the description to disambiguate beyond what the empty schema already shows. The description correctly implies an unfiltered enumeration rather than a targeted lookup.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a verb ("discover and deduplicate") and a resource (Objective-C and Swift protocol labels), so the general intent is graspable. But it never states the scope of the discovery — which binary, session, or image the protocols come from — and gives no distinction from the sibling get_objc_classes, which an agent would plausibly confuse it with.

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 when-to-use guidance, no prerequisite (e.g. an open binary/session), and no reference to any alternative tool. The agent must guess whether this is a session-wide enumeration or tied to a prior selection.

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