Skip to main content
Glama

List Dashboard Structure Tool

list-dashboard-structure
Read-onlyIdempotent

List collections and stories the current user can view. A collection is included only when it has at least one visible story. user_role is manager for collection managers and viewer otherwise.

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-dashboard-structure"
  }
}

Input Schema

NameRequiredDescriptionDefault
spaceNoSpace slug. Required when the token is bound to more than one space. Omit it when the token has one space.
project_idNoOptional project id. When omitted, stories from every permitted project are returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds genuine behavioral context beyond that: results are permission-scoped to the current user, a collection is only emitted when it has at least one visible story, and user_role is 'manager' for collection managers and 'viewer' otherwise. It does not cover ordering, pagination, or empty-result behavior.

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?

Three short sentences, front-loaded with the core action and scope, with no filler or restatement of the title. The final sentence about user_role is terse and would read more clearly if it said the field is on the returned objects, but it is still compact and purposeful.

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?

With no output schema and two optional parameters, the description carries the burden of describing return shape; it discloses the collection/story hierarchy and one output field, which is helpful. It omits the story object's contents, result ordering, pagination, and what an empty result looks like. Adequate for a simple read-only list tool, but with visible gaps.

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 100%, so both parameters (space, project_id) are already fully documented in the schema, including the multi-space condition and the default of all permitted projects. The description adds nothing about the parameters, which is acceptable at full coverage but earns only the baseline. The user_role sentence describes an output field, not an input parameter.

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 opens with a specific verb and resource pair: 'List collections and stories the current user can view.' That is enough for an agent to distinguish it from sibling list tools such as list-spaces or list-projects. It stops short of naming or contrasting any alternative explicitly, so it is clear but not differentiated at the level of a 5.

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?

Usage is only implied: the tool returns what the current user is permitted to see, so it fits discovery/browsing scenarios. The description gives no explicit when-to-use or when-not-to-use guidance and does not point to a sibling for a different shape of query. The inclusion rule for collections is output-shaping, not selection guidance.

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