Skip to main content
Glama

MemBrowse

List symbols

list_symbols
Read-only

List the largest symbols in one build of a target, optionally filtered by region, section, source file, object or name, or totalled per section, library, object, file or directory with 'group_by'. Use it to see what takes the space.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>",
      "target": "<target>"
    },
    "name": "list_symbols"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoThe build: a full commit SHA, a SHA prefix (7+ characters), or a branch or tag name. Default: the head of the default branch.
limitNoMaximum rows to return (default 50, max 200).
offsetNoRows to skip, for paging (default 0).
regionNoOnly this memory region, e.g. FLASH or RAM.
targetYesTarget name (see list_targets).
detailsNoAdd address, binding, line, object and archive to each symbol (default false).
projectYesThe project: a public project's GitHub 'owner/repo' (no API key needed), or, with an API key, a project id or name from list_projects.
sectionNoOnly this section, e.g. .bss.
group_byNoReturn totals per group instead of symbols. 'section' sizes whole sections, including string literals no symbol names ('unnamed_bytes'); name_contains then matches the section name.
file_containsNoOnly symbols whose source file path contains this text (case-insensitive).
name_containsNoOnly symbols whose name contains this text (case-insensitive).
object_containsNoOnly symbols whose archive or object file path contains this text (case-insensitive).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the meaningful constraint that results are scoped to a single build and enumerates the filtering dimensions, but it says nothing about cost, rate limits, or what happens with anonymous versus API-key access on large targets.

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, front-loaded with the core action, then the optional filters, then the purpose. Every clause carries information and nothing is repeated, which is exactly right for a twelve-parameter tool whose schema does the heavy lifting.

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

Completeness4/5

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

For a 12-parameter read-only tool with no output schema, the description covers both return modes and all filter axes, and the schema fills in defaults. It falls just short by not pointing at sibling tools (export_symbols, list_targets) or clarifying how the grouped totals differ in shape from the symbol rows.

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 every parameter is already documented, including the group_by enum and the default branch behavior of ref. The description adds meaning only by summarizing which filter dimensions exist and by noting that group_by returns totals instead of symbols, which the schema already states in more detail.

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 ("list the largest symbols in one build of a target") plus scope limits (one build, one target) and the two operating modes: filtered symbol listing and grouped totals. It never names its closest sibling, export_symbols, so the agent must infer the boundary itself.

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

Usage Guidelines3/5

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

"Use it to see what takes the space" implies the intended investigative use, and the group_by clauses describe a second mode. There is no when-not guidance, no mention of export_symbols for extraction, and no note that project/target discovery happens via list_projects/list_targets, so the routing is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources