Skip to main content
Glama
Sign In
idf-mcp

idf-mcp

by intent-driven-software
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Agent: generate report

agent_generate_report

Generate a portfolio-level performance and risk report with recommendations by providing portfolio ID and report type.

Instructions

Robo-advisor generates a portfolio-level performance / risk report as a recommendation.

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_generate_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
portfolioIdNoportfolioId — FK to Portfolio
reportTypeNoreportType

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false. The description adds that the report is a 'recommendation' but does not disclose whether it creates a persistent object, requires permissions, or has side effects beyond generation. Minimal behavioral context beyond 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?

The description is a single sentence of 10 words, highly concise. It front-loads the core action and resource with no redundant information.

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?

The tool is simple with 2 params and no output schema. The description does not specify the output format or behavior (e.g., synchronous, return type). While sufficient for basic understanding, it lacks details on what the agent receives after generation.

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?

Input schema coverage is 100% with descriptions for portfolioId and reportType. The description adds no additional meaning beyond the schema. Baseline score of 3 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?

The description clearly states the tool generates a portfolio-level performance/risk report as a recommendation. The verb 'generates' and resource 'report' are specific. It distinguishes from siblings like agent_execute_preapproved_order (execution) and agent_propose_rebalance (rebalancing proposal).

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 generating reports but provides no explicit guidance on when to use this tool versus alternatives. No exclusions or conditions are mentioned, leaving the agent to infer context.

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