Skip to main content
Glama

MemBrowse

Export symbol table

export_symbols
Read-only

Get one build's whole symbol table as a file, to analyse with code (Python, pandas, DuckDB, jq) when the other tools cannot answer the question. Returns a one-time download, not the symbols: run the returned 'command' in a shell to save the file, then work on the file, so the table never enters the conversation. Needs a shell that can reach the MemBrowse server.

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": "export_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.
targetYesTarget name (see list_targets).
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly, non-destructive, closed-world) by disclosing the crucial behavior: the call does NOT return symbols, it returns a one-time download command that must be run in a shell. That changes how an agent must handle the result and would be invisible from the schema or annotations alone, and the note that the table never enters the conversation sets expectations about context cost.

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?

Three sentences, front-loaded with purpose followed by return semantics and then the shell prerequisite; each sentence carries needed information. Slightly dense phrasing ('Returns a one-time download, not the symbols') but no filler.

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?

For a tool with no output schema, the description fully explains what comes back (a command, not data) and what the agent must do next, along with the environment requirement. An agent can call this correctly and interpret the result without further information.

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 ref (SHA/prefix/branch/tag with default), target, and project. The description adds nothing about parameter semantics, which is acceptable given the schema's completeness but merits only the baseline 3.

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?

States a specific verb and resource ('Get one build's whole symbol table as a file') plus the scope ('one build's whole'). It also distinguishes itself from the sibling tools by positioning itself as the fallback 'when the other tools cannot answer the question'.

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 clear selection rule — use this when the other tools cannot answer the question and when the result needs code-based analysis — and states the prerequisite (a shell that can reach the MemBrowse server). It stops short of naming a specific sibling to use instead for normal lookups, so the routing is implicit rather than exhaustive.

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