Skip to main content
Glama
Hookflo
by Hookflo

list_platforms

Discover supported webhook platforms with their signature algorithms, header names, and special notes for integration.

Instructions

List all webhook platforms supported by Tern with their signature algorithm, header name and any special notes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function `listPlatforms` fetches supported webhook platforms from the data source and returns them.
    export async function listPlatforms() {
      return {
        count: PLATFORMS.length,
        platforms: PLATFORMS.map((p) => ({
          id: p.id,
          name: p.name,
          algorithm: p.algo,
          headerName: p.header,
          secretNote: p.secretNote,
          specialNote: 'specialNote' in p ? p.specialNote : null,
        })),
        note: 'All platforms support optional queue, retry, DLQ and alerting via @hookflo/tern reliability layer',
      }
    }
  • src/index.ts:68-76 (registration)
    Registration of the `list_platforms` tool in the `ListToolsRequestSchema` handler.
    {
      name: 'list_platforms',
      description: 'List all webhook platforms supported by Tern with their signature algorithm, header name and any special notes.',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • The execution logic for `list_platforms` in the `CallToolRequestSchema` handler.
    } else if (name === 'list_platforms') {
      result = await listPlatforms()
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses this is a listing operation that returns platform details, but doesn't mention behavioral aspects like whether it requires authentication, has rate limits, returns paginated results, or what happens on errors. The description adds basic context but misses important operational details.

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?

The description is a single, efficient sentence that front-loads the core purpose ('List all webhook platforms') and then specifies the return details. Every word earns its place with zero redundancy or wasted space.

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?

For a zero-parameter listing tool with no output schema, the description adequately explains what information is returned. However, without annotations or output schema, it should ideally mention the return format (e.g., array of objects) and any limitations. The description is complete enough for basic use but lacks operational context.

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 has zero parameters (schema coverage 100%), so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, focusing instead on what the tool returns. No parameter information was needed or expected.

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 clearly states the specific action ('List all webhook platforms') and resource ('supported by Tern'), including what information is returned ('signature algorithm, header name and any special notes'). It distinguishes this read-only listing tool from siblings like add_webhook (creation) and verify_signature (validation).

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

Usage Guidelines4/5

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

The description implies this tool should be used when needing to understand available webhook platforms and their configurations, which provides clear context. However, it doesn't explicitly state when NOT to use it or name specific alternatives among the sibling tools (like get_capabilities which might overlap).

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/Hookflo/tern-mcp'

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