LociHub

List nodes

list_nodes

Read-only

Browse the owner's own nodes (title + address) when there is no query. Not for finding something specific: search does that.

order = recent (newest first, default) or name (A-Z); limit caps the rows (default 50). Rows carry title, address, type, visibility and url, no bodies (hydrate reads one). address narrows it to one folder of the owner's, e.g. loci://<handle>/.inbox/** for the files waiting to be filed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_nodes"
  }
}

Input Schema

Name	Required	Default
`limit`	No
`order`	No	recent
`address`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Adds substantial context beyond the annotations: the exact returned fields (title, address, type, visibility, url), the exclusion of bodies, the defaults (recent, 50), and folder scoping. It does not say what happens when more than 50 rows exist (truncation vs. paging) or whether any auth/handle constraints apply, which are the remaining behavioral unknowns for a list operation.

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?

Four short sentences, front-loaded with purpose and the sibling exclusion, then parameters, then return shape and scoping. Every sentence carries information; formatting is used to highlight parameter names rather than pad.

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 compensates well by enumerating returned fields and noting bodies are omitted. The one gap is the absence of any statement about result-set limits beyond 'limit caps the rows' — an agent cannot tell whether a full listing requires paging or repeated calls.

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%, so the description carries the full burden and does: 'order' is enumerated as recent (default) or name (A-Z), 'limit' is described as capping rows with its default, and 'address' is explained as narrowing to one folder with a concrete example pattern. All three parameters gain meaning not present in the schema.

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 ('Browse the owner's own nodes (title + address)') and immediately names the sibling it is not ('Not for finding something specific: search does that'). An agent can distinguish it from search, hydrate, and outline without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use condition ('when there is no query') and an explicit when-not with the alternative ('search does that'), plus a pointer to hydrate for bodies. Nothing is left to inference about tool selection.

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

All LociHub tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?