Skip to main content
Glama

Customer feedback interview planner

toolfound_feedback_interview_planner
Read-onlyIdempotent

Create a bounded interview plan and evidence log from a learning goal, participant count, and available time. Returns an evidence-bounded result and the canonical web tool URL.

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": {
      "goal": "<goal>",
      "participants": "<participants>",
      "minutes": "<minutes>",
      "stage": "<stage>"
    },
    "name": "toolfound_feedback_interview_planner"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYesThe one product decision the interviews should inform, written as a sentence such as Decide which onboarding step to simplify.
stageYesWhere the people you interview are with your product: evaluating it, new users, active users, or people who stopped using it. This picks the opening question.
minutesYesLength of each interview in minutes, as a whole number, for example 30.
participantsYesHow many people you can interview, as a whole number.

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
linksYes
errorsNo
summaryYes
sectionsYes
canonical_result_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / goal / description
      Added value: +"The one product decision the interviews should inform, written as a sentence such as Decide which onboarding step to simplify."
    • addedInput schema / properties / minutes / description
      Added value: +"Length of each interview in minutes, as a whole number, for example 30."
    • addedInput schema / properties / participants / description
      Added value: +"How many people you can interview, as a whole number."
    • addedInput schema / properties / stage / description
      Added value: +"Where the people you interview are with your product: evaluating it, new users, active users, or people who stopped using it. This picks the opening question."
  2. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond that: the plan is 'bounded' and results are 'evidence-bounded', and it discloses that the return includes the canonical web tool URL. It does not explain what 'bounded' actually constrains or how the evidence log is limited.

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?

Two sentences, front-loaded with the verb and resource, with no filler. The second sentence is slightly redundant ('evidence-bounded result' echoes 'evidence log'), but the whole thing is tight and scannable.

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

Completeness3/5

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

An output schema exists, so the description does not need to enumerate return values, and the fully described schema carries the parameter burden. However, for a tool whose value depends on being picked over other planning tools, the absence of any usage or scoping guidance leaves a real gap.

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 all four parameters, including the 'stage' enum, are already fully documented in the schema; baseline 3 applies. The description restates three of the four inputs but omits 'stage' entirely, so it adds no meaning beyond the schema and misses the one parameter whose enum semantics drive the opening question.

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?

The description uses a specific verb ('Create') and a concrete resource ('bounded interview plan and evidence log'), then enumerates the inputs that shape it (learning goal, participant count, available time). That is enough to distinguish it from the launch/marketing siblings, but it never names or contrasts a specific alternative tool, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives. The only signal is the implicit framing of turning a learning goal into an interview plan, which the agent must infer from the tool name and the 'goal' parameter.

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