Skip to main content
Glama

Resolve Native Call Targets

resolve_native_call_targets
Idempotent

Resolve a single static native call site from typed provider references, keeping ambiguous targets as candidates and computed calls as unknown without executing code or traversing a call graph.

Instructions

Resolve one explicit static call site using typed provider call references. Preserves ambiguous targets as candidates and unresolved computed calls as unknown; does not execute code or traverse a call graph.

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_native_call_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes
documentNoExact provider document or program identity.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare idempotent=true, destructive=false, openWorldHint=false, and readOnlyHint=false, so the safety profile is already visible. The description adds real outcome semantics beyond that data: ambiguous targets are preserved as candidates and unresolved computed calls come back as unknown, and it states that no code is executed. It does not explain why the operation is not read-only, but it still adds meaningful behavioral context.

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, each carrying distinct information, with the core action stated first and the exclusions and edge-case outcomes following. No filler or repeated phrasing.

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 only 50% parameter coverage, the description carries some of the load by describing candidates and unknown outcomes. It still leaves the address format and the shape of returned candidate/unknown results unstated, which is a gap for a resolver tool with an undocumented required parameter.

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 50%: document carries a description, but address (required) is only a bare string ref with no explanation of the expected format. The description hints at provider-scoped, explicit-call-site semantics but does not clarify the address syntax or how document alters resolution. The baseline of 3 fits because the description neither compensates for nor repeats schema detail.

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

Purpose5/5

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

The description names a specific verb (resolve) and a narrowly scoped resource (one explicit static call site), and it explicitly rules out two adjacent behaviors (execute code, traverse a call graph), which separates it from graph-traversal siblings such as get_call_graph and build_call_path.

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?

It conveys a clear context ('one explicit static call site using typed provider call references') and states when not to expect this behavior ('does not execute code or traverse a call graph'). It stops short of naming a specific alternative tool to use for graph traversal, so it is strong but not fully explicit routing.

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