Skip to main content
Glama
Sign In
Browser Feedback MCP

Browser Feedback MCP

by itk-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_widget_snippet

Get the HTML snippet to add browser feedback collection to a web app; deprecated, prefer the browser extension setup.

Instructions

Deprecated — prefer the browser extension (setup_extension). Get the HTML snippet to add to a web app for browser feedback collection.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_widget_snippet"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it discloses the most important behavioral trait: deprecation and the preferred successor. It does not describe auth needs, side effects, or output format beyond 'HTML snippet', which keeps it 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.

Conciseness5/5

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

Two clauses with zero waste, and the deprecation warning is front-loaded before the functional description so the agent sees the routing signal first.

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?

For a no-param, no-output-schema helper, the description supplies everything needed: what it returns (an HTML snippet), why (browser feedback collection), and the deprecation path. Nothing required to invoke it correctly is missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the schema is trivially complete. Baseline 4 applies for a no-parameter tool.

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 ('Get the HTML snippet to add to a web app for browser feedback collection'), which lets an agent distinguish it from install_widget and the other feedback siblings without opening a 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 labels the tool deprecated and names the replacement (setup_extension), giving the agent a clear routing decision. The condition that selects the alternative is stated rather than inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools