Skip to main content
Glama
benswel

QR for Agent

by benswel
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

list_webhooks

View all registered webhook endpoints for your API key to monitor event notifications from the QR code platform.

Instructions

List all registered webhook endpoints for your API key. The HMAC secret is not included for security.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • packages/mcp/src/tools.ts:677-684 (handler)
    The handler for the 'list_webhooks' tool, which performs an API request to fetch registered webhooks.
    list_webhooks: {
  description:
    "List all registered webhook endpoints for your API key. The HMAC secret is not included for security.",
  inputSchema: z.object({}),
  handler: async () => {
    return apiRequest("/api/webhooks");
  },
},

Tool Definition Quality

A4.2/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. Adds valuable security context that 'HMAC secret is not included'—critical behavioral info about response contents that schema cannot convey.

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 total. First states purpose immediately; second adds security constraint. Zero redundancy—every sentence earns 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?

No output schema exists, but description mitigates by noting what is excluded from response (HMAC secret). Could improve by briefly noting what fields ARE included, but sufficient for a zero-parameter list operation.

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?

Zero parameters present per schema. With 0 params, baseline is 4 as per specification guidelines.

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?

Specific verb 'List' + resource 'webhook endpoints' + scope 'for your API key' clearly defines the operation. Distinct from siblings create_webhook and delete_webhook, and entirely different from QR code tools.

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

Usage Guidelines3/5

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

No explicit when/when-not guidance or alternatives mentioned. However, usage is implied by the verb 'List' contrasting with sibling 'create_' and 'delete_' prefixes. Adequate but not explicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/benswel/qr-agent-core'

If you have feedback or need assistance with the MCP directory API, please join our Discord server