Skip to main content
Glama

Procedure Address

procedure_address
Idempotent

Resolve a procedure symbol name or provider-normalized address to its canonical entry address, keeping external address spaces explicit.

Instructions

Resolve an unambiguous procedure symbol name or provider-normalized address to its canonical entry address. External address spaces remain explicit.

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": {
      "procedure": "main"
    },
    "name": "procedure_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentNoThe active target's provider document name; use open_binary to switch targets
procedureYesThe procedure name or address

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?

Annotations already disclose idempotence, non-destructiveness, and closed-world behavior. The description adds a useful scope constraint that external address spaces remain explicit, but it does not explain why readOnlyHint is false or what side effect makes this more than a pure lookup.

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 is short and front-loaded, with the core resolve action stated first. The second sentence about external address spaces is compact but somewhat cryptic and would benefit from a little more explanation.

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 two-parameter resolver with no output schema, the description covers the basic transformation and return target. However, it leaves gaps around the return format, ambiguity handling, document scoping, and what 'external address spaces remain explicit' means operationally.

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 description coverage is 100%, so the schema already documents both parameters. The description adds marginal meaning by saying the procedure input should be unambiguous and provider-normalized, but it says nothing additional about the document parameter and does not clarify accepted address formats.

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 names a specific verb and resource: resolve a procedure symbol name or provider-normalized address to its canonical entry address. That distinguishes it reasonably well from address-oriented siblings, though it does not explicitly contrast itself with tools like address_name or goto_address.

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 explicit when-to-use guidance, no prerequisites, and no alternatives named. The purpose implies a use case, but the description does not say when this resolver should be chosen over sibling address or procedure tools.

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