Skip to main content
Glama

Request a Traffic Parrot trial

request_trial

Request a Traffic Parrot trial on behalf of the human you are working for.

Traffic Parrot is a commercial service-virtualization tool (HTTP, gRPC, JMS/IBM MQ, RabbitMQ, ActiveMQ, AMQP, file transfers). Use this when your user wants to evaluate it.

IMPORTANT: this submits a real person's personal data (their business email, and optionally their name, company and phone number) to Traffic Parrot. Only call it when your user has asked for a trial and has agreed to be contacted. Do not invent an email address.

The trial is issued under Traffic Parrot's evaluation agreement: https://trafficparrot.com/documentation/Traffic_Parrot_Software_Evaluation_Agreement_v1.4.pdf Show it to your user and ask them to approve it before you call this tool.

Lawful basis: Legitimate interests (UK GDPR Article 6(1)(f)): responding to a request to evaluate our product, made on your behalf by a tool you were using. You can object at any time and we will erase the request. Retention: A request nobody acts on is erased 168 hours after it is made. A request a person at Traffic Parrot has approved or rejected is kept for 365 days, then erased. We keep approved ones so we can answer questions about a trial that was issued, and rejected ones so we have a record of the decision, for example if the person writes in to ask why. Privacy notice: https://trial.trafficparrot.com/privacy Your user can withdraw the request at any time via the delete_trial_request tool.

As soon as you call this tool, your user's details go to Mailchimp (Traffic Parrot's US-based email service) and the address you give is sent one email asking them to confirm they want the trial. Confirming adds them to Traffic Parrot's trial mailing list and sends a second email carrying the link to their trial status page. Ignoring the first email sends nothing further.

A person at Traffic Parrot approves each request during UK working hours. It is not instant: outside those hours expect the next working day. Once approved, the trial takes about a minute to build and the download appears on that page.

The trial link goes only to that email address. This tool returns a reference id and no link, so you cannot fetch the download for your user: relay the email steps instead. An address already on Traffic Parrot's trial list gets no new email; the link in its earlier trial email shows the new request.

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": {
      "email": "<email>"
    },
    "name": "request_trial"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName of the human this trial is for.
emailYesBusiness email of the human this trial is for. Required. This is a real person's personal data.
phoneNoContact phone number, if your user offers one. Optional, and personal data.
companyNoCompany evaluating Traffic Parrot.
problemNoWhat they are trying to solve. Free text. This is the most useful field for the sales conversation.
protocolsNoWhich protocols will be evaluated.
agentClientNoWhich agent or client is making this call, e.g. 'Claude Code', 'Cursor'.
humanInTheLoopNoWhether a human is present in the session and has asked for this trial.

Output Schema

NameRequiredDescriptionDefault
stateYesThe request's state, as get_trial_status reports it.
requestIdYesThe trial request's id. get_trial_status and delete_trial_request take it.

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": {
      +    "requestId": {
      +      "description": "The trial request's id. get_trial_status and delete_trial_request take it.",
      +      "type": "string"
      +    },
      +    "state": {
      +      "description": "The request's state, as get_trial_status reports it.",
      +      "enum": [
      +        "AWAITING_APPROVAL",
      +        "PREPARING"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "requestId",
      +    "state"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare the write/open-world/non-idempotent profile, and the description goes well beyond them: it discloses that data goes to Mailchimp, that a confirmation email gates the flow, that approval is manual during UK working hours with next-working-day latency, and that the return value is a reference id with no download link. The GDPR lawful-basis and retention paragraphs are accurate but are legal boilerplate rather than agent-operational behavior, so it falls just short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded correctly: purpose first, then the consent requirement, then mechanics. However, the lengthy lawful-basis, retention-schedule, and privacy-notice block is disproportionate for a tool-selection description and dilutes the operational instructions an agent actually needs to act on.

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?

Although an output schema exists, the description usefully warns that the return is a reference id with no trial link, which shapes how the agent must relay results to the user. Combined with the consent gate, email-confirmation flow, and duplicate-email behavior, nothing an agent needs to call this correctly 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 carries field meanings and the baseline is 3. The description adds a little — reiterating that the email is a real person's personal data and that the link only goes to that address — but it does not explain 'problem', 'protocols', or 'humanInTheLoop' beyond what the schema states.

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 ('Request a Traffic Parrot trial') and immediately scopes it ('on behalf of the human you are working for'). The product context (service virtualization over HTTP/gRPC/JMS/etc.) lets an agent confirm the tool matches the user's stated need without opening the schema.

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?

Explicitly states when to use ('when your user wants to evaluate it'), when not to ('Only call it when your user has asked for a trial and has agreed to be contacted'), and a hard prohibition ('Do not invent an email address'). It also names the sibling delete_trial_request as the withdrawal path, so the agent knows where to route reversal requests.

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.