Skip to main content
Glama

Send feedback to Padlet

send_feedback
Read-only

Tell Padlet's developers about a problem with these tools: confusing behaviour, a missing capability, or a problem you worked around, even if you completed the task. The user does not need to ask. Do not include personal information, student content or secrets.

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": {
      "feedback": "<feedback>"
    },
    "name": "send_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNo
feedbackYesWhat happened and what you expected.
telemetryNoOptional. Padlet records this to improve its tools; it does not change what the tool does.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false and idempotentHint=false, so the safety profile is covered. The description adds real context beyond that: the proactive-send policy and the data-handling restriction on what may be included. It does not disclose that repeated calls produce separate reports (non-idempotent) or who can see the feedback, which is the main remaining behavioral unknown.

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?

Two sentences, both load-bearing: the first defines the purpose and the trigger conditions, the second handles consent and data hygiene. The proactive instruction is front-loaded rather than buried, and there is no restatement of the tool name or title.

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?

For a fire-and-forget reporting tool with full annotations and no output schema, the definition covers what to send, when to send it unprompted, and what must be excluded. It is only short of complete on the non-idempotency implication and on how `telemetry.intent` should be phrased, though the schema itself partially documents the latter.

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 coverage is 67% and each parameter already carries a description, so the baseline is 3. The description does add meaningful constraint on the `feedback` payload (exclude personal information, student content and secrets) that the schema does not state, but it says nothing about `context.tool` or the optional `telemetry.intent`, leaving those to the schema.

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?

The description opens with a specific verb and recipient ('Tell Padlet's developers') and enumerates the kinds of problems it covers (confusing behaviour, missing capability, worked-around problem). This is unmistakably not a Padlet-content CRUD operation, so it is easily separated from every listed sibling.

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?

It gives explicit when-to-use triggers ('confusing behaviour, a missing capability, or a problem you worked around, even if you completed the task') and an explicit autonomy instruction ('The user does not need to ask'), plus a when-not constraint on content (no personal info, student content or secrets). No alternative tool exists for this purpose, so the absence of named siblings 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.