Skip to main content
Glama

heistclips feature requests

list_feature_requests
Read-onlyIdempotent

The public heistclips feature-request board: every request with its upvotes and status (requested, building, shipped), most upvoted first. Use before request_a_feature to find an existing request to upvote instead.

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

Input Schema

NameRequiredDescriptionDefault
statusNoOnly this status

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuinely new behavior: the board is public, results are complete (every request) rather than paginated, and they come back sorted by upvote count. Pagination/result-size behavior is only implied by 'every request' and never stated outright.

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 sentences, both front-loaded with the most useful facts (what the board is, then the workflow guidance) and no restatement of the tool name or padding.

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

Completeness4/5

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

For a one-parameter read tool with no output schema, the description conveys both the call purpose and the shape of the return (requests, upvotes, status, ordering). Minor gaps remain around result volume and whether upvote data is a plain count, but nothing needed to invoke it correctly is missing.

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 coverage is 100% and the single status parameter carries its enum and description, so the schema does the work. The description repeats the three status values but adds no filtering syntax or interaction detail (e.g., what happens when status is omitted), so baseline 3 applies.

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 names the specific resource (the public heistclips feature-request board), its scope (every request), the fields returned (upvotes, status with its three enumerated values), and the ordering (most upvoted first). It also implicitly contrasts itself with request_a_feature, so an agent can tell it is the read/list counterpart rather than a mutation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to use it before request_a_feature to find an existing request to upvote instead, which routes the agent away from a duplicate-creation path. It stops short of saying when to apply the status filter versus listing everything, so it is strong but not exhaustive.

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.