Skip to main content
Glama

Current Procedure

current_procedure
Idempotent

Retrieve the analyzed procedure at Hopper's GUI cursor position, enabling context-aware analysis without a procedure-name lookup.

Instructions

Return the analyzed procedure containing Hopper's current cursor. This uses GUI cursor state and is not a procedure-name lookup.

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": {},
    "name": "current_procedure"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.7/5.0
Behavior3/5

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

Annotations mark this as neither read-only nor destructive with idempotentHint=true, yet the description only says "Return," implying a pure read with no side effects. That does not outright contradict the annotations, but the description leaves unexplained why a retrieval tool is flagged non-read-only (likely that it triggers analysis of the cursor target) and says nothing about behavior when the cursor is outside any procedure.

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 short sentences, zero filler, with the operative definition front-loaded and the disambiguation second. Every clause earns its place.

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, the description carries the burden of explaining the return value, and "the analyzed procedure" is left vague — an agent cannot tell what fields or shape to expect. The core selection semantics are complete, but the return-side description is thin for a tool whose whole purpose is producing an object.

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?

There is a single optional `document` parameter at 100% schema description coverage, so the schema already explains its meaning and how to switch targets via open_binary. The description adds nothing about the parameter, which is acceptable only because the schema is fully documented.

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?

States a specific verb and resource ("Return the analyzed procedure containing Hopper's current cursor") and explicitly carves out a contrast with name-based lookups, which separates it from the procedure_* family. It stops short of naming a specific sibling, but the cursor-based vs. name-based axis is clear enough for an agent to choose correctly.

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?

Gives a positive selection condition (use when you want the procedure under the GUI cursor) and an explicit exclusion ("is not a procedure-name lookup"), which routes an agent away from name-keyed alternatives. No prerequisites or failure conditions (e.g., what happens when the cursor is not inside a procedure) are mentioned.

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