Skip to main content
Glama

source_fields

Profile a source’s recent event fields—coverage, distinct counts, top values, and declared labels/keys—before choosing labels, ensuring every label field uses an exact, existing field name.

Instructions

Profile a source's real fields from recent events: every candidate field with its coverage, distinct count, and top values, plus which are already declared as labels/keys. Call this BEFORE choosing labels for a source — a label's field MUST be one of these exact field names (never invent one). The labels block echoes the source's current declared axes.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and largely does: it discloses that results derive from recent events (so coverage is sampled, not absolute), what the `labels` block echoes, and the strict constraint it enforces on downstream label definitions. It does not state read-only/safety posture, auth requirements, or what happens when a source has no recent events, which keeps it short of a 5.

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?

Three tight sentences, front-loaded with the action and payoff, then the ordering rule, then the return structure. No filler and no repetition of the tool name.

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?

An output schema exists, so return values need not be spelled out, and the description still frames them usefully alongside the critical pre-label workflow rule. The remaining hole is the undocumented `limit` parameter and the absence of any safety/permission note for a tool with no annotations.

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?

Schema description coverage is 0%, so the description must compensate and only partly does: `name` is inferable as the source identifier from "a source's real fields." The `limit` parameter (default 500) is never mentioned, leaving unclear whether it caps sampled events, returned fields, or top values — a meaningful ambiguity for a profiling tool whose accuracy depends on sample size.

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 — profiling a source's real fields from recent events — and enumerates the payload (coverage, distinct count, top values, existing label/key declarations). An agent can tell this is an introspection/profiling tool rather than a mutation or discovery tool without opening the schema.

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 explicit sequencing guidance: "Call this BEFORE choosing labels for a source" plus the hard constraint that a label's `field` must be one of the returned exact names, never invented. It lacks an explicit when-not condition or a named alternative tool, but the workflow placement is unambiguous.

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