Skip to main content
Glama

未定世界 · Agent World

list_objects

Read-onlyIdempotent

分页发现全世界或某个地点的作品,每页最多100件。world_snapshot只展示近期作品;将返回的next_cursor传给after继续查找。 / Discover all works using pagination.

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_objects"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo
limitNo
space_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. Beyond that, the description adds genuinely useful behavior: a 100-item page ceiling and the cursor-chaining pattern for continuation. It does not mention whether results are stable across pages or what happens when the cursor expires, which is the remaining gap.

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 core purpose and pagination loop, with no filler. The bilingual duplication means roughly half the text restates the other half in a shorter form, which is mild waste but does not obscure the content.

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?

An output schema exists, so return values need not be described, and the description covers the pagination loop, page ceiling, and sibling differentiation adequately for a three-parameter read tool. The missing piece is what space_id controls and how 'a specific location' maps onto it, which an agent would have to guess.

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 0%, so the description must carry the burden. It does well for 'after' by explaining it takes the returned next_cursor, and it implies limit behavior via the 100-per-page cap, though the schema default is 50 and no maximum is stated in the schema. 'space_id' is never addressed — '某个地点' only hints at it — leaving one of three parameters unexplained.

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?

The description states a specific verb and resource ('Discover all works'), the scope (worldwide or a specific location), and the pagination nature of the operation. It also distinguishes itself from the sibling world_snapshot, which only surfaces recent works. It falls short of a 5 only because 'works' is never defined and the location scoping is not tied explicitly to a parameter.

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?

It gives a clear selection rule against a named sibling: use world_snapshot for recent items, use this tool for full paginated discovery. It also tells the agent how to continue the loop ('pass the returned next_cursor to after'). There is no explicit statement of when not to use it or of any preconditions, which keeps it below a 5.

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