Microservice.MD

Find event consumers

find_event_consumers

Read-only

Find which services consume a specific event and which publish it, from saved versions across your catalog. Call before renaming, removing or changing the shape of an event, and report the affected services and teams to the user. For everything that depends on a service, use find_dependents. An event no service uses returns empty lists, not an error. Services in the unsaved list could not be checked.

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": {
      "event": "<event>"
    },
    "name": "find_event_consumers"
  }
}

Input Schema

Name	Required	Description	Default
`event`	Yes	The exact event name, case-sensitive, for example `PaymentCaptured`.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

changedInput schema / properties / event / description

Previous value: -"The event name, for example `PaymentCaptured`."New value: +"The exact event name, case-sensitive, for example `PaymentCaptured`."

First observedNov 9, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and destructiveHint false, so safety is covered; the description goes well beyond that by disclosing that an unused event returns empty lists rather than an error, that results are scoped to 'saved versions', and that services in the unsaved list could not be checked — a silent partial-result caveat an agent would otherwise misread as a complete answer.

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?

Four short sentences, zero waste, ordered purpose-first then trigger, alternative, and edge-case semantics. The partial-results caveat is placed last where it works as a post-call caution rather than cluttering the primary action.

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 one-parameter read with no output schema, the description covers purpose, trigger, alternative, empty-result behavior, and coverage gaps — nearly everything an agent needs. It does not sketch the actual result structure (e.g., separate consumer vs. publisher lists, or where team names come from), which an agent must discover by calling.

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?

With a single parameter at 100% schema description coverage, the schema already explains the exact case-sensitive event name and gives an example. The description adds only the 'saved versions' scoping, not any naming, casing, or format guidance beyond the schema, so the baseline 3 applies.

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 plus a bidirectional scope: 'which services consume a specific event and which publish it, from saved versions across your catalog.' The later sentence naming find_dependents as the service-oriented alternative lets an agent separate this tool from its closest sibling 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?

Gives an explicit trigger ('before renaming, removing or changing the shape of an event'), an explicit exclusion with a named alternative ('For everything that depends on a service, use find_dependents'), and a downstream instruction to report affected services and teams to the user.

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

All Microservice.MD tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?