Skip to main content
Glama

mark_observation

Adds a time-stamped label to a captured HTTP observation using its ID, letting you tag traffic evidence for later analysis; marks are temporal evidence, not proof of causality.

Instructions

Add a label to an observation at the current time. Requires observation_id and label. Marks are temporal evidence, not proof of causality.

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": {
      "observation_id": "<observation_id>",
      "label": "<label>"
    },
    "name": "mark_observation"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelYes
observation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the mutating, non-idempotent profile is covered structurally. The description usefully reinforces this by scoping the mark to "the current time" and clarifying its evidentiary status, but it says nothing about label uniqueness, duplicate handling, or what happens with an invalid observation_id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and the scope qualifier. The middle sentence restating the required parameters is largely redundant with the schema's required list, which is the only wasted text.

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 simple two-parameter mutation with annotations present and no output schema, the description covers purpose and a semantic caveat adequately. It leaves gaps on return value (whether a mark identifier comes back) and failure modes, which matter for a non-idempotent write.

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% for both parameters, so the description carries the burden and largely fails it. It only restates that observation_id and label are required, adding no meaning about label format, length, allowed characters, or what an observation_id looks like.

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?

"Add a label to an observation at the current time" gives a specific verb (add a label) and resource (observation), and the "current time" qualifier separates it from flow-capture siblings such as begin_observation or capture_status. It stops short of naming an alternative explicitly, so it is clear but not fully differentiated.

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 statement of when to use this versus begin_observation, end_observation, or capture_status, and no prerequisites or exclusions. The line "Marks are temporal evidence, not proof of causality" is an interpretive caveat about the resulting data, not invocation guidance.

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