Skip to main content
Glama

Resolve Containing Procedure

resolve_containing_procedure
Idempotent

Resolve any address—interior instruction or external entry—to its provider-analyzed containing procedure. Negative results distinguish outside segments from not-in-a-procedure without guessing.

Instructions

Resolve an arbitrary address, including an interior instruction or exact external entry, to its provider-analyzed containing procedure. A negative result distinguishes outside segments from not in a procedure and is never guessed from nearby symbols.

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": {
      "address": "0x1000"
    },
    "name": "resolve_containing_procedure"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesA provider-normalized address; default memory uses 0x-prefixed hexadecimal
documentNoThe active target's provider document name; use open_binary to switch targets

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations, the description discloses a real behavioral trait: negative results are reliable and never inferred from nearby symbols, which tells the agent how much to trust an empty answer. Annotations cover idempotency and non-destructiveness; the readOnlyHint=false value is not contradicted ("resolve" makes no read-only claim, and provider analysis may cache state), though the tension is not addressed.

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

Conciseness5/5

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

Two sentences, front-loaded with the core action and followed by the one caveat an agent needs about negative results. No redundant restatement of the name, title, or schema.

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 only two fully documented parameters and no output schema, the definition covers the essential contract, including the semantic difference between an outside segment and a non-procedure address. What the return object actually contains is implied only loosely, but nothing required to invoke the tool correctly is missing.

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?

Schema coverage is 100%, so the baseline would be 3, but the description adds meaning the schema lacks: the address may point at an interior instruction rather than a function entry, which materially affects how the agent should construct the argument. The document parameter is left entirely to the schema, which already explains switching targets via open_binary.

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?

"Resolve an arbitrary address ... to its provider-analyzed containing procedure" states a specific verb and resource, and the phrase "including an interior instruction or exact external entry" pins down the input scope precisely. It does not name a sibling such as current_procedure or procedure_address, so differentiation is implied by scope rather than stated.

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 description makes clear the tool is for mapping any address (interior or external entry) to a procedure, which implies its use case, and it hints that "outside segments" and "not in a procedure" are distinct outcomes. However, it never states when to prefer this over the sibling procedure_* tools or when not to use it.

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