Skip to main content
Glama

heap_end_action

End a heap request phase and retrieve chunk records with filtering by event type, caller, address, or action. Includes raw delta JSON for heap exploitation analysis.

Instructions

结束当前请求/堆操作阶段,返回该请求创建的 chunk 记录。

在单个网络请求或单个 connect/close 操作处理完毕、GDB 暂停后调用。 默认输出按请求粒度映射的 heaplog 风格记录,例如: [calloc] nmemb=0x1 size=0x46 total=0x46 user=... chunk_addr=... chunk_sz=... caller=... [malloc] size=0xec user=... chunk_addr=... chunk_sz=... caller=... 同时附带 Raw Delta JSON,供后续自动分析。

Args: event_types: 可选,逗号分隔事件类型/分组过滤,如 "alloc", "free", "malloc,calloc", 留空表示全部。 caller_contains: 可选,按 caller 符号子串过滤,如 "SLPParseSrvUrl"、"SLPBufferAlloc"。 action_contains: 可选,按 action 名称子串过滤。 addr_start: 可选,按 chunk/user 地址范围起点过滤,支持十六进制。 addr_end: 可选,按 chunk/user 地址范围终点过滤,支持十六进制。 around_addr: 可选,查看某地址附近的堆事件。 around_size: around_addr 半径。 limit: 最多返回多少条事件。 include_raw: 是否附带 Raw Delta JSON;调堆风水时可设 False 减少噪声。

Returns: JSON 格式的堆变化增量数据,包含: - action_id: 操作标识 - events: 详细事件列表 - delta: 增量汇总(新分配数、新释放数、详情) - summary: 一行文本摘要 - cumulative: 累计状态

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
addr_endNo
addr_startNo
around_addrNo
around_sizeNo
event_typesNo
include_rawNo
action_containsNo
caller_containsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Without annotations, the description details the output format (JSON with action_id, events, delta, summary, cumulative) and mentions Raw Delta JSON. It explains parameter effects like include_raw. No side effects are described, but none expected for this type of action.

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 description is front-loaded with the purpose and structured with Args and Returns sections. It is somewhat lengthy due to examples, but each part adds value for a complex tool.

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?

Given 9 parameters, no annotations, and an output schema, the description covers all aspects: when to call, how to filter, and what to expect in the response. It is complete for an agent to correctly invoke the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description provides thorough explanations for all 9 parameters with examples (e.g., event_types, caller_contains, around_addr). This fully compensates for the lack of schema descriptions.

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 clearly states the tool ends a heap action phase and returns chunk records. The Chinese and English text specify the purpose, and it distinguishes itself from siblings like heap_begin_action.

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?

The description provides explicit context: call after a network request or connect/close operation when GDB is paused. It does not explicitly mention when not to use or alternatives, but the context is clear enough.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Aiyakami/PWN-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server