FeatureJet

publish_board

Publish a board so it is live at its public URL.

    OFF BY DEFAULT. Putting a board on the public internet is a human
    decision: unless the FeatureJet deployment has opted in, this returns
    403 `publish_disabled` and the owner publishes from the dashboard.
    Where it is enabled it needs a `write` (or `admin`) scoped key and an
    active subscription -- an org without one gets 403
    `subscription_required`.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries full burden for behavioral transparency. It discloses that publishing is off by default, requires specific scopes and subscription, and returns 403 errors in certain cases. This provides good insight into the tool's behavior beyond the basic operation.

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?

The description is concise with two paragraphs: the first states the purpose, and the second adds important usage constraints. It is front-loaded and every sentence adds value, though the error details could be formatted more succinctly.

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 the tool's complexity (publishing to public internet, auth, subscription), the description covers key constraints and error scenarios. The output schema exists, so return values need not be explained. However, the lack of parameter explanation is a gap for completeness.

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

Parameters2/5

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

The input schema has one required parameter 'slug' with 0% description coverage. The description does not explain what the slug is, how to obtain it, or any format requirements. This adds minimal meaning beyond the schema definition.

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 the core action: 'Publish a board so it is live at its public URL.' It distinguishes from siblings like 'unpublish_board' by explicitly describing the publishing action and its prerequisites.

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?

The description provides explicit conditions for use: off by default, requires opt-in, write/admin scoped key, and active subscription. It lists error cases (403) when these are not met, giving clear guidance on when the tool should and should not be used.

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

All FeatureJet tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0

Disambiguation5/5

All tools have clearly distinct purposes. The board, post, comment, vote, analytics, changelog, queue, and utility tools each target different resources or actions without overlap.

Naming Consistency4/5

Most tools follow verb_noun snake_case (e.g., create_board, get_post). Two tools (ping, whoami) are not verb_noun but are standard conventions, keeping overall consistency high.

Tool Count5/5

22 tools is well-scoped for a feedback board management server. Each tool covers a distinct operation without unnecessary duplication or bloat.

Completeness4/5

Covers core lifecycle for boards (CRUD + publish/unpublish), posts (CRUD + claim/release + status proposal + evidence), and comments (create/list). Missing comment update/delete and vote creation, but these are minor gaps for the domain.

Resources

Need Help?