Skip to main content
Glama

aga_start_monitoring

Start or restart behavioral monitoring with a new baseline to enforce security policies and track AI agent tool usage.

Instructions

Start or restart behavioral monitoring with a new baseline.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
behavioral_baselineNo

Implementation Reference

  • The handler function for the aga_start_monitoring tool which resets the behavioral monitor and optionally sets a new baseline.
    export async function handleStartMonitoring(args: StartMonitoringArgs, ctx: ServerContext) {
      if (!ctx.portal.artifact) return ctx.error('No artifact loaded. Call aga_create_artifact first.');
      if (ctx.portal.state !== 'ACTIVE_MONITORING') return ctx.error(`Cannot start monitoring in state ${ctx.portal.state}`);
    
      ctx.behavioralMonitor.reset();
      if (args.behavioral_baseline) {
        ctx.behavioralMonitor.setBaseline(args.behavioral_baseline);
      }
    
      return ctx.json({
        success: true,
        portal_state: ctx.portal.state,
        monitoring_active: true,
        baseline_set: !!args.behavioral_baseline,
      });
    }
  • Input schema/interface for aga_start_monitoring.
    export interface StartMonitoringArgs {
      behavioral_baseline?: BehavioralBaseline;
    }
  • src/server.ts:152-165 (registration)
    Registration of aga_start_monitoring tool with its schema definition and handler.
    // 6. aga_start_monitoring (governed)
    governedTool('aga_start_monitoring',
      'Start or restart behavioral monitoring with a new baseline.',
      {
        behavioral_baseline: z.object({
          permitted_tools: z.array(z.string()),
          rate_limits: z.record(z.number()),
          forbidden_sequences: z.array(z.array(z.string())),
          window_ms: z.number(),
        }).optional(),
      },
      async (args) => handleStartMonitoring(args, ctx),
    );
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'behavioral monitoring' but doesn't disclose what monitoring entails (e.g., logs alerts, blocks actions), whether it's destructive to existing data, authentication needs, rate limits, or side effects. 'Start or restart' implies mutation but lacks behavioral details, leaving significant gaps for a tool that likely controls system behavior.

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 a single, efficient sentence with zero waste. It's front-loaded with the core action ('Start or restart behavioral monitoring') and adds necessary context ('with a new baseline'). Every word earns its place, making it highly concise and well-structured.

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?

Given the tool's complexity (behavioral monitoring control), lack of annotations, no output schema, and 0% schema coverage, the description is incomplete. It doesn't explain what monitoring does, how it interacts with other tools (e.g., 'aga_measure_behavior'), or what happens upon execution. For a mutation tool with rich parameter structure, this leaves too many unknowns.

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?

Schema description coverage is 0%, so the description must compensate. It mentions 'with a new baseline,' which hints at the 'behavioral_baseline' parameter but doesn't explain its structure or semantics (e.g., what 'permitted_tools' or 'forbidden_sequences' mean). This adds minimal value beyond the schema, meeting the baseline for low coverage without fully compensating.

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 the action ('Start or restart behavioral monitoring') and the resource ('with a new baseline'), providing a specific verb+resource combination. It distinguishes from siblings like 'aga_measure_behavior' or 'aga_trigger_measurement' by focusing on initialization/restart rather than ongoing measurement. However, it doesn't explicitly differentiate from all siblings, keeping it at 4 rather than 5.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., whether monitoring must be stopped first), when to restart versus start fresh, or which sibling tools (like 'aga_measure_behavior' for ongoing tracking) serve complementary purposes. Without any usage context, this scores low.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/attestedintelligence/aga-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server