Skip to main content
Glama
Sign In
@originchain/telemetry-mcp

@originchain/telemetry-mcp

Official
by originchain-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

top_patterns

Retrieve the most frequent log patterns from telemetry rollup data. Specify a limit to control the number of patterns returned.

Instructions

The highest-volume log patterns, instant from the rollup.

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": "top_patterns"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does mention that results come from the rollup and are instant, which hints at pre-aggregated, likely read-only behavior, but it does not state side effects, freshness, limits, or any operational caveats.

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 extremely concise, with no filler words. The core result ('highest-volume log patterns') is front-loaded, and the behavioral qualifier ('instant from the rollup') is secondary but relevant. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, but with no output schema, no annotations, and no parameter documentation, more context is needed. The description does not clarify what 'log patterns' means, how many are returned by default, or what the output shape looks like, leaving the agent with an incomplete picture.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has one optional 'limit' parameter with 0% description coverage. The description does not mention limit or any parameter semantics, forcing the agent to infer meaning from the name alone. Because schema coverage is low, the description should compensate but does not.

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?

The description clearly states that the tool returns the highest-volume log patterns and identifies the data source (the rollup). It conveys the resource and result well, though it lacks an explicit verb and does not differentiate it from siblings by name.

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

Usage Guidelines2/5

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

There is no guidance on when to use top_patterns versus alternatives like similar_patterns, log_volume, or recent_events. The 'instant from the rollup' hint implies a fast, precomputed query, but no explicit when-to-use or when-not-to-use context is provided.

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