Skip to main content
Glama

Send a test event

runheed_send_test_event

Sends one test error (RunheedTestEvent) to a project through the normal ingest path, which shows whether the project and its send key work. The test error appears in the recent errors and can be resolved like any other.

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": {
      "projectId": "<projectId>"
    },
    "name": "runheed_send_test_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesProject id or slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations only say it is a non-destructive, non-idempotent write with no open-world access; the description adds the crucial side effect that a real error is persisted and shows up in recent errors, and that it can be resolved like any other. It does not warn that repeated calls create multiple events (relevant given idempotentHint=false) or mention any rate limits.

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 tight sentences, zero filler, with the action and its diagnostic purpose front-loaded before the side-effect note.

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, non-destructive diagnostic tool with no output schema and full annotation coverage, the definition explains enough: what it does, what it proves, and what artifact it leaves behind. Minor gap is the absence of any note on returned identifiers or repeat-call behavior.

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?

Only one parameter (projectId) and schema coverage is 100%, with the schema already documenting 'Project id or slug'. The description adds no further meaning about the parameter, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Sends one test error (RunheedTestEvent) to a project') plus the mechanism ('through the normal ingest path'). This is clearly distinct from the read-only siblings like runheed_get_recent or runheed_list_projects, though it never names a sibling explicitly.

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?

Gives a clear use context: verifying that a project and its send key work. It does not state when NOT to use it (e.g., in production projects) or name any alternative diagnostic, so it falls short of full when/When-not guidance.

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.