Skip to main content
Glama

Suggest an idea

suggest_idea

Suggest a feature or change to Kinetune for others to vote on Posts an idea to the Community board in the app, where everyone signed in can vote and comment, and Kinetune says what is planned and what shipped. Use it when the person asks for something the product can't do yet ("I wish it could…"): say it in their words, one line, with how they would use it in body. It is public to Kinetune's users under the person's name, so leave out private links and contact details, and ask before posting. Suggesting votes for the idea and follows it: the person hears by email when it ships. At most 5 a day.

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": {
      "title": "<title>"
    },
    "name": "suggest_idea"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoWhat it is about: lyric-video, canvas, music-video, or everything (the whole app)everything
bodyNoHow they would use it: their release, the platform, why it matters
titleYesThe idea in one line, in the person's words

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations, which only say this is a non-readonly, non-destructive, non-idempotent write. The description discloses that the post is public and attributed to the person's name, that suggesting auto-votes and follows the idea, that an email arrives on ship, and that there is a 5-per-day rate limit.

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 core action is front-loaded and every clause carries information, but it is one long run-on paragraph that packs public visibility, drafting guidance, notification behavior, and rate limits together. Slight structural tightening would help, though nothing is padded.

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

Completeness5/5

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

For a three-parameter write tool with no output schema, the description covers everything an agent needs: what gets created, where it appears, who sees it, the safety preconditions, the side effects, and the throttling limit. Nothing material 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 description coverage is 100%, so the schema already documents title, body, and the area enum. The description restates the title/body intent in prose ('one line, in their words… how they would use it in body') but adds little beyond the existing field descriptions and never mentions the area parameter. 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?

States a specific verb and resource: posts an idea to Kinetune's public Community board where users vote and comment. This is unmistakably distinct from every sibling, all of which operate on artists, songs, videos, or looks.

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?

Gives an explicit trigger condition ('when the person asks for something the product can't do yet'), the phrasing to use, and a hard exclusion ('leave out private links and contact details, and ask before posting'). No sibling tool could be confused for this action, so the absence of named alternatives is not a gap.

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