Skip to main content
Glama
rampify-dev

Rampify MCP Server

list_feature_specs

Browse and filter feature specifications by status, priority, type, tags, module, or source. Get an overview of specs with progress and aggregate counts.

Instructions

Browse and filter all feature specifications for a project. Returns an overview of specs with status, priority, and task progress.

Use this to answer questions like "what's in progress?", "what's planned?", or "show me all high-priority specs". For full spec details (criteria, tasks, affected files), follow up with get_feature_spec using a spec_id from the results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoSite domain (e.g., "example.com"). Uses SEO_CLIENT_DOMAIN env var if not provided.
project_idNoProject UUID — use instead of domain when no domain is configured. Uses RAMPIFY_PROJECT_ID env var if not provided.
statusNoFilter by status (e.g., ["planned", "in_progress"]). Omit to return all.
priorityNoFilter by priority. Omit to return all.
feature_typeNoFilter by feature type. Omit to return all.
tagsNoFilter by tags.
moduleNoFilter by source module (e.g., "seo" for SEO scan findings).
sourceNoFilter by source (e.g., "user" for manual specs, "seo_scan" for findings).
include_statsNoInclude aggregate counts by status and priority (default: false).
Behavior4/5

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

No annotations provided, but the description implies a read-only operation by saying 'browse and filter' and 'returns an overview'. It doesn't mention side effects, but for a listing tool this is sufficient. Could add more about env var fallbacks.

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?

Four sentences, no fluff. Each sentence serves a purpose: purpose, return type, example queries, follow-up instruction. Well-structured and easy to scan.

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?

Given 9 optional parameters and no output schema, the description provides sufficient context: return type (overview with status/priority/task progress), filter capabilities (by status, priority, etc.), and stats option. Could elaborate on exact return fields.

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?

Schema coverage is 100% so baseline is 3. The description adds value by explaining how parameters like domain/project_id fall back to env vars and gives example usage ('what's planned?'), enhancing understanding beyond schema.

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 clearly states it is for browsing/filtering feature specs, specifies it returns an overview with status/priority/task progress, and distinguishes from get_feature_spec by directing users to that tool for full details.

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

Usage Guidelines5/5

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

The description explicitly tells when to use this tool (to answer questions like 'what's in progress?') and when to follow up with get_feature_spec for full details, providing clear usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rampify-dev/rampify-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server