Skip to main content
Glama

Feedback: Request feature

feedback_request_feature
Destructive

Send a feature request or improvement idea to the Nilyo team as a tracked issue: a missing action, provider or capability, a workflow that needs too many steps, a confusing result. Use when the user asks for something Nilyo cannot do yet, or explicitly wants to suggest an improvement, and agrees to send it. Describe the user's goal and why current tools fall short. Ask the user for consent first (user_consent=true).

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>",
      "description": "<description>",
      "user_consent": "<user_consent>"
    },
    "name": "feedback_request_feature"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolNoNilyo tool name involved, if any.
titleYesShort, specific title in English (what fails or what is wanted), e.g. 'email_list_messages fails on OVH IMAP mailbox with 501'.
providerNoProvider involved when relevant: linkedin, whatsapp, instagram, telegram, gmail, outlook, imap, calendar.
use_caseNoConcrete scenario the user wanted to achieve and how often it happens.
workaroundNoWhat the user does today instead, if anything.
descriptionYesWhat the user was trying to do, in their words plus your observations. No passwords, tokens, message contents or third-party personal data.
user_consentYesMust be true: the user explicitly agreed to send this report to the Nilyo team.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Adds real context beyond the annotations: the report is sent to an external party (the Nilyo team) as a tracked issue, and a user consent gate is mandatory before sending. That the consent is a hard requirement is also encoded in the schema, and the description does not restate the irreversibility implied by destructiveHint=true, but the external-submission and consent behavior is the important disclosure here.

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?

Three tight sentences: purpose first, then trigger conditions, then content guidance, then the consent gate. Slight redundancy in repeating the user_consent=true requirement already enforced by the schema's const, but it is a safety-critical instruction so the cost is low.

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?

With 7 params but full schema coverage and no output schema, the description covers what an agent needs to decide and call: intent, trigger, content to include, and the consent prerequisite. It does not describe what happens after submission (e.g., whether a tracking reference is returned), which would help close the loop for the user.

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, but the description adds content-level guidance not in the schema: describe the user's goal and why the current tools fall short. This steers how to fill description/use_case fields rather than merely restating them.

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: send a feature request or improvement idea to the Nilyo team as a tracked issue, and enumerates what qualifies (missing action, provider, capability, multi-step workflow, confusing result). It does not name the closest sibling feedback_report_bug, so the boundary between 'feature request' and 'bug report' is left for the agent to infer.

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?

Gives an explicit trigger condition: the user asks for something Nilyo cannot do yet, or explicitly wants to suggest an improvement, and agrees to send it. It does not state when NOT to use it, notably how to route to feedback_report_bug when the complaint is about broken behavior rather than a missing capability.

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.