Skip to main content
Glama

List Story Widgets Tool

list-story-widgets
Read-onlyIdempotent

List widgets in a story. query and fixed_filters are included only for collection managers. Viewers receive null for both because they cannot see widget SQL or fixed filters.

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": {
      "story_id": "<story_id>"
    },
    "name": "list-story-widgets"
  }
}

Input Schema

NameRequiredDescriptionDefault
spaceNoSpace slug. Required when the token is bound to more than one space. Omit it when the token has one space.
story_idYesNumeric story id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered; the description adds genuinely new behavioral context by disclosing that 'query' and 'fixed_filters' are permission-gated fields that come back null for viewers who cannot see widget SQL or fixed filters. That is a real, non-obvious response-shape caveat that the annotations cannot convey. It stops short of describing pagination or the overall widget object.

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?

Two tight sentences with the core action front-loaded and no filler. Minor deduction because 'query' and 'fixed_filters' are introduced without being labeled as returned fields, which costs a beat of clarity.

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 (one required param, full schema coverage, no output schema), and the description covers the permission caveat, but with no output schema it should say more about what a widget entry contains and whether results are paginated. Adequate rather than complete for an unannotated return shape.

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, story_id) are already fully documented, establishing the baseline of 3. The description's mention of 'query' and 'fixed_filters' refers to response fields rather than inputs, so it adds no input-parameter meaning and could momentarily suggest parameters that do not exist.

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 widgets in a story') with a clear scope qualifier, which cleanly separates it from siblings like list-story-filters and list-dashboard-structure. It stops short of naming any sibling explicitly, so it lands just under the top mark.

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?

The description gives no when-to-use or when-not-to-use guidance and does not route the agent to any alternative. The only usage signal is the implied 'you have a story and want its widgets', which the agent must infer from the resource name alone.

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