Skip to main content
Glama

MemBrowse

List targets

list_targets
Read-only

List a project's build targets (firmware binaries) with the current used and limit size of each memory region at the head of the default branch.

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

Input Schema

NameRequiredDescriptionDefault
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

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the description's added value is scope: results are pinned to the head of the default branch, not an arbitrary commit. It also discloses that each entry carries used-vs-limit per memory region, which tells the agent what data is available without a follow-up call. Auth handling is left to the schema.

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?

One sentence, front-loaded with the verb and resource, then the return content, then the branch scope. No filler or redundant restatement of the title.

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 single-parameter read tool with full schema coverage and complete annotations, the description supplies enough: what a target is, what fields come back, and which branch is read. Minor gaps remain around pagination/result size and behavior for an unknown or inaccessible project, but nothing blocks a correct call.

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 parameter with 100% schema description coverage, and that schema already explains the public 'owner/repo' form versus an API-key project id or name. The description adds nothing beyond 'a project's', so the baseline of 3 applies.

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?

Specific verb plus resource ("List a project's build targets") and it disambiguates the term by equating targets with firmware binaries. It also states what accompanies each target (used and limit size per memory region), so an agent knows the shape of the result. It does not explicitly contrast itself with siblings like compare_builds or get_memory_history, keeping it short of a 5.

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

Usage Guidelines2/5

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

The description states what the tool returns but gives no when-to-use framing, no exclusions, and no routing to alternatives such as list_projects or get_memory_history. The only implied usage is 'discover a project's targets', which the name already conveys.

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