Skip to main content
Glama

document_list

List documents, newest first. One row per language version; siblings share language_group_id.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo
searchNo
project_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations at all, the description carries the full disclosure burden. It does add real value by disclosing ordering (newest first) and row granularity (one row per language version, siblings share language_group_id), which an agent could not infer. However it says nothing about pagination via cursor, default/max page size, permission requirements, or what fields a row contains.

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?

Two short sentences with zero filler, and the core behavior plus the most surprising semantic detail are front-loaded. Nothing is redundant or padded.

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 no annotations, so the description must cover everything; instead it omits pagination semantics, filtering behavior, default result size, and return fields for a four-parameter list tool. The row-granularity note is helpful but insufficient for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and all four parameters (limit, cursor, search, project_id) are undocumented in both schema and description. The description adds no meaning about what search matches, whether project_id scopes the list, or how cursor paging interacts with the newest-first ordering, so it fails to compensate for the coverage gap.

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?

States a specific verb and resource ("List documents") plus a non-obvious result shape: one row per language version, with siblings linked via language_group_id. That granularity note meaningfully distinguishes it from document_get, though it never names a sibling explicitly.

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?

No when-to-use or when-not-to-use guidance. The description never says how this differs from document_get for a single document, or whether search/project_id filtering is the intended path versus document_list of another resource. Usage is only implied by the verb "List".

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