Skip to main content
Glama

begin_observation

Bookmark a new observation starting now, optionally scoped by exact host, and return an ID and start cursor for later API traffic analysis without starting capture.

Instructions

Bookmark a new observation starting now, optionally scoped by exact host. Does not start capture or clear traffic. Returns id and start_cursor.

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

Input Schema

NameRequiredDescriptionDefault
hostNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the bar is lower, yet the description adds real value by clarifying what it does NOT do (no capture start, no traffic clearing) and what it returns (id and start_cursor). It does not mention duplicate-observation behavior across repeated calls, which is the one remaining gap.

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 short sentences, front-loaded with the core action, then the exclusions, then the return values. Every sentence earns its place with no filler.

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?

Complete enough for a one-parameter bookmark tool: it covers the action, the scoping option, the non-behaviors, and the returned identifiers even though no output schema exists. Minor gaps remain around the global (no-host) case and how start_cursor is consumed downstream.

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

Parameters4/5

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

The schema documents nothing for the single `host` parameter (0% coverage), so the description carries the burden — it does so by stating the parameter is optional and that matching is by exact host, implying no wildcards or subdomain expansion. That is meaningful semantics beyond the schema, though format details are not given.

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?

Names a specific verb and resource ("Bookmark a new observation starting now") plus a scoping option ("optionally scoped by exact host"). This is clearly distinguishable from capture-control siblings thanks to the explicit negatives, though it stops short of naming the sibling it complements (e.g., end_observation/mark_observation).

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

Usage Guidelines3/5

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

Gives useful negative guidance — it does not start capture or clear traffic — which steers agents away from treating it as a capture control. However, it never states the positive condition (when to bookmark vs. when to use end_observation or mark_observation), leaving the agent to infer the workflow.

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