Skip to main content
Glama

List Strings

list_strings
Idempotent

Lists all provider-defined string objects or filters by address, returning address/value pairs with encoding, terminator status, and byte length when available.

Instructions

List every provider-defined string object, or filter to one address, as address/value pairs with encoding, terminator status, and byte length when available. Hopper reads complete typed objects and retains its original display text as provider_value; long literals may span adjacent unterminated objects.

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": "list_strings"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressNoA provider-normalized address; default memory uses 0x-prefixed hexadecimal
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
Behavior4/5

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

Beyond the annotations, it discloses the return shape, the provider_value/display-text convention, and a real caveat that long literals may span adjacent unterminated objects — the kind of edge case an agent cannot infer from schema or hints. It does not address volume/limits for large binaries, and the readOnlyHint=false annotation sits oddly against an operation described purely as reading.

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?

Two sentences, front-loaded with the action and scope, then the output contract and the one caveat. Dense but every clause carries information; the second sentence is slightly compressed in phrasing but not padded.

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?

With no output schema, the description correctly takes on the burden of describing the returned fields and the provider_value convention. It is complete for correct invocation; the only omission is any statement about result size or behavior on large targets.

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 coverage is 100%, so both parameters are already documented in structured form, giving a baseline of 3. The description adds only the notion that address acts as a filter to a single object; the document parameter and the 0x-prefixed address format are left entirely to the schema.

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?

"List every provider-defined string object, or filter to one address" gives a specific verb, resource, and scope, and the output shape (address/value pairs with encoding, terminator status, byte length) pins down what a 'string object' means here. It does not name search_strings, so the boundary with the obviously adjacent sibling is left to inference.

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?

The description states two modes of use: enumerate everything, or narrow to a single address via the filter. That is clear framing, but there is no explicit exclusion such as 'use search_strings when you have a query rather than an address', so the choice against the sibling tool is only implied.

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