Skip to main content
Glama
Sign In
Finagent MCP

Finagent MCP

by finuchetai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_passport

Read-onlyIdempotent

Reads the report passport to show methodology, data origin, completeness, and demo limitations before you query financial data.

Instructions

Read the methodology, data origin, completeness and demo limitations first.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this a read-only, idempotent, closed-world operation, so the safety profile is covered. The description adds meaningful context by disclosing that the output documents data origin, completeness and 'demo limitations' — a caveat about data reliability that annotations cannot express. It still doesn't say what form the content takes (text, markdown, structured object) or how large it is.

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?

A single short sentence with the timing cue ('first') front-loaded and no filler. It is efficient, though the imperative phrasing is slightly less informative than a declarative statement of the resource would be.

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 zero parameters, no output schema and annotations covering the safety profile, the definition supplies enough to call it correctly and to know it should be consulted before the financial siblings. A brief note on the return format would close the remaining gap.

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 no parameters, so there is nothing for the description to disambiguate; the baseline applies. The description spends no words on parameter semantics, which is correct here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Read' and the enumerated contents (methodology, data origin, completeness, demo limitations) give a rough sense that this returns a metadata/provenance document, but the term 'passport' is never defined and the sentence reads as an instruction rather than a statement of what the tool returns. It is not explicitly differentiated from the sibling data getters.

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 word 'first' implies this should be called before the other tools, which is genuine sequencing guidance. However, no alternatives are named and there is no statement of when to skip it or how it relates to get_balances/get_pnl/list_months.

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