Skip to main content
Glama
Sign In
headlo-mcp

headlo-mcp

Official
by headlohq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_collections

List all collections in the active workspace to view and manage your data. Retrieve a complete overview of available collections.

Instructions

List all collections for the active workspace

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

Input Schema

NameRequiredDescriptionDefault
workspace_idNoWorkspace ID — omit to use the first workspace from context

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description must disclose behavioral traits. 'List' implies a read-only operation, but the description does not state return format, pagination, ordering, or side effects. The scoping to 'active workspace' adds some context but not full transparency.

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?

The description is a single, front-loaded sentence with no filler. It efficiently communicates the core function without unnecessary detail.

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

Completeness3/5

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

The tool is simple with one optional parameter and no output schema. The description covers the essential purpose but omits details about the return value structure and any edge cases (e.g., empty workspace, permissions). It is adequate but minimal, leaving room for improvement.

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?

The only parameter, workspace_id, is fully described in the schema with 100% coverage. The description adds no extra parameter semantics beyond what the schema already provides, so the baseline of 3 is appropriate.

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?

The description 'List all collections for the active workspace' uses a specific verb (List) with a clear resource (collections) and scope (active workspace). It clearly distinguishes from sibling tools like create_collection, update_collection, list_records, and list_pages.

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 gives context ('active workspace') but provides no explicit guidance on when to use this tool versus alternatives. No exclusions or complementary tools are mentioned, leaving the decision to the agent's inference from the tool name.

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