Skip to main content
Glama

Send Traffic Parrot a feature request

submit_feature_request

Send a feature request or product feedback to the Traffic Parrot team. Use this when your user wants something Traffic Parrot does not currently do. If you include a contact email it is a real person's personal data, so only include one your user has agreed to share.

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>",
      "detail": "<detail>"
    },
    "name": "submit_feature_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoContact email, if the user is willing to share one. Optional.
titleYesOne-line summary of the requested feature.
detailYesWhat the feature should do and why it is needed.
agentClientNoWhich agent or client is making this call.

Output Schema

NameRequiredDescriptionDefault
sentYesThe feature request was sent to the Traffic Parrot team.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / email / format
      Removed value: -"email"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "sent": {
      +      "const": true,
      +      "description": "The feature request was sent to the Traffic Parrot team.",
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "sent"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag this as a non-read-only, non-idempotent, non-destructive write; the description adds genuinely useful context about personal data handling in the optional email. It stops short of saying what a duplicate submission does or what confirmation the agent gets, which the non-idempotent hint makes relevant.

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?

Three short sentences, front-loaded with the action, then the trigger condition, then the one caveat that could cause harm if missed. No filler.

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?

An output schema exists so return values need no explanation, and all four parameters are documented. The only remaining gap is post-submission behavior (confirmation, duplicate handling) for a non-idempotent external send.

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 the baseline is 3, and the description earns an extra point by adding a consent constraint on the email field ('only include one your user has agreed to share') that the schema itself does not state.

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 ('Send a feature request or product feedback') plus the recipient ('the Traffic Parrot team'), which cleanly separates it from the trial-request and documentation siblings.

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 a clear triggering condition: 'Use this when your user wants something Traffic Parrot does not currently do.' It does not explicitly name an alternative tool, but no sibling overlaps enough to require a routing note.

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.