Skip to main content
Glama
Sign In
idf-mcp

idf-mcp

by intent-driven-software
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Agent: recompute risk score

agent_recompute_risk_score

Recomputes risk profile for a portfolio or all portfolios. Updates risk assessment to reflect current holdings.

Instructions

Robo-advisor recomputes the risk profile for a portfolio (or all portfolios if portfolioId omitted).

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

Input Schema

NameRequiredDescriptionDefault
portfolioIdNoportfolioId — FK to Portfolio

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations show readOnlyHint=false and destructiveHint=false; the description adds minimal extra context. It doesn't disclose side effects like database updates or performance implications, but it aligns with annotations.

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, front-loaded with key action, no wasted words. Efficient and to the point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one optional parameter and no output schema, the description provides essential information: what it does and the scope behavior. No gaps.

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 covers portfolioId with a description, but the description adds that omitting it recomputes for all portfolios—valuable context beyond the schema.

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?

The description clearly states the action ('recomputes the risk profile') and the resource ('portfolio'), and distinguishes from siblings like agent_execute_preapproved_order or agent_propose_rebalance.

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?

The description implies usage for recomputing risk scores but lacks explicit guidance on when to use vs alternatives or when to omit portfolioId. The mention of omitting portfolioId is a helpful scope detail.

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