Skip to main content
Glama

Wall of Decks

list_sections

List the slide sections (problem, team, traction, ask and so on) with how many slides each has and how common it is across decks.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full disclosure burden; it does describe the returned content, which is valuable given there is no output schema. It never defines the scope of 'across decks' (all decks the caller can access? all decks in the workspace? a sample?), nor does it mention any permissions or pagination behavior. For a zero-parameter read-only listing this is a modest but real gap rather than a blocker.

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?

A single sentence that front-loads the verb and resource, then lists the returned metrics. Nothing is padded. The only soft spot is the trailing 'and so on', which slightly dilutes the otherwise precise enumeration of section examples.

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, the description must convey the return shape and it partially does by naming slide counts and cross-deck frequency. It omits the scope of the deck population, the ordering of results, and whether the response is a list, a map, or an aggregate. For a very simple zero-parameter tool this is adequate rather than complete.

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

Parameters4/5

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

The tool takes no parameters and the schema is an empty object, so there is no parameter meaning for the description to add. Baseline for a zero-parameter tool is 4, and nothing here misleads about inputs.

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 gives a specific verb ('List') and resource ('slide sections'), and even names example values (problem, team, traction, ask) that make the resource concrete. It also states the two data points returned, slide counts and cross-deck commonality. It stops short of distinguishing itself from the closely related sibling 'section_benchmarks', so it isn't 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?

There is no explicit when-to-use, when-not-to-use, or alternative-naming guidance. The stated output (section counts plus how common each section is across decks) implies an enumeration/aggregation use case, which an agent can reasonably infer. However, the overlap with the sibling 'section_benchmarks' is left entirely unaddressed.

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