Skip to main content
Glama
Sign In
idf-mcp

idf-mcp

by intent-driven-software
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Agent: flag anomaly

agent_flag_anomaly

Raises portfolio-level alerts with custom severity and message to flag anomalies.

Instructions

Robo-advisor raises a portfolio-level alert with severity.

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": {
      "severity": "<severity>",
      "message": "<message>"
    },
    "name": "agent_flag_anomaly"
  }
}

Input Schema

NameRequiredDescriptionDefault
severityYesseverity
messageYesmessage

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations mark readOnlyHint false and destructiveHint false; description adds that it raises an alert. No extra behavioral context beyond what annotations and name imply.

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?

Single sentence with no redundant words. Front-loaded and efficient.

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?

Tool is simple with two string params and no output schema. Description adequately covers purpose and behavior; minor gap on expected severity values but acceptable.

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 coverage is 100% and description adds no extra meaning beyond parameter names. Baseline score is appropriate.

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?

Description states specific verb 'raises' and resource 'portfolio-level alert' with severity. Distinguishes from siblings which involve orders, signals, reports, rebalancing, risk scores.

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?

No explicit when-to-use or when-not-to-use guidance. Implied by purpose but not stated; sibling tools are distinct but no alternatives mentioned.

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