Skip to main content
Glama
Sign In
Finagent MCP

Finagent MCP

by finuchetai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_months

Read-onlyIdempotent

Lists monthly periods, their closed/open status, and report availability so you can identify which months can be queried; open periods are not queryable.

Instructions

List periods, closed/open state and available reports. Open periods cannot be queried.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so the safety profile needs no restating. The description still adds a genuine behavioral constraint beyond the annotations: open periods are unqueryable, which changes how an agent should interpret the returned state. It stops short of describing ordering or pagination.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with the return content and followed by the key constraint. Every sentence carries information, though the opening clause is slightly compressed and could separate what is listed from the states more cleanly.

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?

With no output schema, the description must carry the return semantics, and it names the three things returned: periods, state, and available reports. That is sufficient for a zero-parameter, read-only listing tool; ordering and empty-result behavior are the only omissions.

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 tool takes zero parameters, so the baseline of 4 applies. There is nothing for the description to disambiguate on the input side, and it correctly adds no redundant parameter talk.

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?

States a specific verb (list) and the returned resource set: periods, their closed/open state, and available reports. The resource is named 'periods' rather than 'months', a minor terminology mismatch with the tool name, and there is no explicit contrast with sibling tools like get_balances or get_pnl.

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 line 'Open periods cannot be queried' implicitly tells the agent to check state before querying data elsewhere, which is useful routing context. However, it never states when to call this tool versus the data-retrieval siblings, nor any prerequisites such as authentication or workspace scoping.

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