Skip to main content
Glama
Sign In
StelaSpace

StelaSpace

Official
by StelaSpace
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

List documents

list_documents

List documents from a space by slug, with optional case-insensitive title search to narrow results.

Instructions

List documents in a space, optionally filtered by a case-insensitive title search term.

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": {
      "spaceSlug": "<spaceSlug>"
    },
    "name": "list_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional case-insensitive term to filter documents by title.
spaceSlugYesSlug of the space to list documents from.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.8/5.0
Behavior3/5

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

Discloses listing behavior and case-insensitive filtering. Lacks details on pagination, ordering, or return format (full documents vs metadata). Without annotations, description carries full burden and is moderately transparent.

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?

Single concise sentence, front-loaded with main action, no unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, and description omits return format, pagination, or limits. For a listing tool, this is a significant gap reducing completeness.

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 covers both parameters (100% coverage). Description adds 'case-insensitive' which is already in schema; adds no new meaning beyond 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?

Clearly states verb 'List', resource 'documents', scope 'in a space', and optional filter. Distinguishes from siblings (list_spaces for spaces, publish_file for publishing).

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?

Explicitly mentions when to use (listing documents with optional title filter). No explicit when-not-to-use, but sibling tools provide context for alternatives.

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