Skip to main content
Glama

Povver — Strength Training

Send Feedback

submit_feedback

Send a bug report, feature request or feedback to the Povver team. Use it when asked, or offer it after an unexpected tool error, a missing capability, a confusing or wrong result, or a workaround you had to use. Send only what the user asked to send: show them the exact text first, and never include other people's data. type: bug · feature_request · feedback. At most 10 per hour.

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": {
      "type": "<type>",
      "message": "<message>"
    },
    "name": "submit_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYes
titleNoA short summary.
messageYesThe text to send, as the user approved it.
client_refNoYour key for this report; the same key again returns the first result and sends nothing new.
prompted_byNoOnly if a Povver note asked for this report: the value that note names.
contact_emailNoOnly if the user wants a reply, and at the address they gave.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / prompted_by
      Added value: +{
      +  "description": "Only if a Povver note asked for this report: the value that note names.",
      +  "enum": [
      +    "feedback_note",
      +    "error_nudge"
      +  ],
      +  "type": "string"
      +}
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), and the description adds real behavioral context beyond them: a hard rate limit of 10 per hour and a consent workflow requiring the user to see the exact text before sending. It does not describe the response or whether a report can be retracted, which is minor for a non-destructive submission tool.

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?

Front-loaded with purpose, then consent rules, then type values and the rate limit — every sentence carries operational weight. The 'type: bug · feature_request · feedback' fragment duplicates the schema enum and is the one piece that doesn't earn its place.

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 6-parameter, 2-required submission tool with no output schema, the description covers purpose, triggers, consent constraints, allowed types and rate limiting, which is enough to call it correctly. Details on the return value and on when prompted_by should be supplied are left to the schema.

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 83%, so the schema already explains title, message, client_ref idempotency, prompted_by and contact_email. The description's only parameter content is the type enum list ('bug · feature_request · feedback'), which merely restates the schema enum, and the 'exact text first' instruction echoes the message field description. Baseline 3 is appropriate given the schema does the heavy lifting.

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 first sentence states a specific verb ('Send') and resource ('a bug report, feature request or feedback to the Povver team'), and immediately enumerates the three supported report types. None of the siblings (log_workout, read_plans, manage_memory, etc.) overlap with this function, so an agent can select it unambiguously.

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?

Explicit when-to-use triggers are given: when the user asks, or after an unexpected tool error, a missing capability, a confusing/wrong result, or a workaround. It also states when-not/how: send only what the user approved, show the exact text first, never include other people's data.

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.