Skip to main content
Glama

Inspect Address Context

inspect_address_context
Idempotent

Inspect a specific reproducible address to retrieve its analyzed name, procedure, comments, and bookmarks; unsupported facets return typed unavailable outcomes.

Instructions

Inspect one explicit reproducible address for its analyzed name, containing procedure, regular and inline comments, and matching bookmarks. Each unsupported facet returns a typed unavailable outcome; use xrefs, assembly, or pseudocode for those deeper views.

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

Input Schema

NameRequiredDescriptionDefault
addressYes
documentNoExact provider document or program identity.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

The valuable addition beyond annotations is partial-result behavior: unsupported facets return a typed unavailable outcome rather than erroring or omitting silently. However, annotations declare readOnlyHint=false for what reads like a pure inspection operation, and the description never explains what non-read-only side effect occurs (analysis triggering, caching, address selection). That leaves a real gap the description should have closed.

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?

Two dense sentences, front-loaded with the core purpose and the returned facets, then the fallback rule. No filler, though the facet list in sentence one is packed enough to be slightly hard to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two parameters, no output schema, and light annotations, the description covers purpose, the shape of a successful result, and the degraded-result case. Nothing an agent needs in order to call it correctly is missing, aside from minor address-format detail.

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 50% and the required 'address' parameter carries no schema description at all; the description's 'explicit reproducible address' mildly signals that symbolic/relative addresses are out of scope. It says nothing about the 'document' parameter's role in disambiguating provider or program identity, so half the params remain unexplained by both schema and prose.

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?

Specific verb + resource: 'Inspect one explicit reproducible address' plus an enumeration of what comes back (analyzed name, containing procedure, regular and inline comments, matching bookmarks). That is far more than the title restated and lets an agent tell it apart from address_name or xrefs, though it never states which siblings cover the same ground positively.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Sentence two routes the agent away: unsupported facets yield a typed unavailable outcome, and deeper views belong to 'xrefs, assembly, or pseudocode'. The conditional routing is explicit, but 'assembly' and 'pseudocode' are not named tools, and no positive trigger ('use this when you have a concrete address and want naming/comments') is spelled out.

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