Skip to main content
Glama

Inspect Native Dispatch Metadata

inspect_native_dispatch_metadata
Idempotent

Inspect a bound provider’s Objective-C and Swift symbol name inventory, returning decoded names with target hashes, coverage, and evidence while flagging unsupported runtime metadata.

Instructions

Inspect the bound provider's name inventory for Objective-C class/method symbols and Swift mangled symbols, returning at most max_records decoded names. Includes target SHA-256 when available, provider identity/version, analysis-profile digest, facet coverage, and per-record Evidence. This is symbol-level evidence, not runtime metadata: ivar layouts, protocol conformances, witness/class tables, and relative pointers are explicitly marked unsupported unless a provider supplies those decoders. The provider controls how its name inventory is acquired.

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": {
      "max_records": 5000
    },
    "name": "inspect_native_dispatch_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_recordsNoMaximum permitted records for this operation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare idempotent, non-destructive, closed-world, and notably readOnlyHint=false; the description supports the non-read-only hint by stating 'The provider controls how its name inventory is acquired.' It goes further than the annotations by enumerating the return payload (target SHA-256, provider identity/version, analysis-profile digest, facet coverage, per-record Evidence) and by explicitly flagging capability gaps.

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?

The definition leads with what the tool does and the record cap, then layers scope boundaries and payload contents. Sentences are dense but each carries information; the closing sentence about provider-controlled acquisition is the weakest in terms of unique value.

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?

With no output schema, the description takes on the burden of describing returns and does so thoroughly, including provenance and Evidence fields. Combined with the explicit unsupported-feature list, an agent has enough to call this correctly, though the lack of any routing to alternative tools for unsupported symbol detail is a remaining gap.

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 parameter is documented, so the baseline applies. The phrase 'returning at most max_records decoded names' clarifies that the cap governs returned records, but that is largely a restatement of the schema's 'Maximum permitted records for this operation.'

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 gives a specific verb and resource: inspecting the bound provider's name inventory for Objective-C class/method symbols and Swift mangled symbols. It also draws a clear scope line against adjacent concepts ('symbol-level evidence, not runtime metadata'), so an agent can distinguish it from the many other inspect_native_* siblings without opening a schema.

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?

There is meaningful implicit guidance in the exclusion list (ivar layouts, protocol conformances, witness/class tables, relative pointers are unsupported), which tells the agent when this tool will not answer a question. However, no alternative tool is named for those cases, and there is no explicit statement of the conditions under which this tool should be preferred.

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