Skip to main content
Glama

Nordic Financial MCP

by io.github.AIDataNordic

ping

Read-only

Connectivity check that confirms the Nordic MCP server process is responding.

Use this at the start of a session to verify the server is reachable before making other calls. Do not use as a proxy for database health — the server can respond while the Qdrant vector database is temporarily unavailable. To confirm data availability, call search_filings directly.

Returns: A greeting string: "Hello {name}! Nordic MCP server is running."

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoArbitrary label included in the response, e.g. 'healthcheck' or 'agent-1'world

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.9/5.0
Behavior5/5

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

The description fully discloses behavior: it returns a greeting string with the input name. This complements the readOnlyHint annotation. There are no contradictions, and the description adds value beyond annotations by specifying the return format.

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?

Three focused sentences: purpose, usage guidelines with alternatives, and return description. No redundant information, front-loaded with the core purpose.

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?

Given the tool's simplicity (1 optional parameter, read-only) and the presence of an output schema, the description covers all necessary aspects: purpose, usage context, caveats, and return value. It is fully complete.

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 already describes the 'name' parameter with 100% coverage. The description adds value by providing usage examples ('e.g. healthcheck or agent-1'), enhancing semantic understanding even though the baseline is 3 due to schema coverage.

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's purpose as a connectivity check for the Nordic MCP server. It uses specific verbs ('confirms', 'respond') and distinguishes itself from sibling tools like search_filings by explicitly stating it is not a proxy for database health.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance: use at session start before other calls, and do not use for database health—instead call search_filings. This directly addresses when to use and when not to, with a clear alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Nordic Financial MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

Each tool has a clear, distinct purpose: analyze_company for synthesized answers, company_research for raw grouped search results, search_filings for direct database queries, get_company_info for registry data, get_current_power_price for electricity prices, parse_pdf_to_text for full document extraction, and ping for connectivity. Descriptions explicitly differentiate them, preventing confusion.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case: analyze_company, company_research, get_company_info, get_current_power_price, parse_pdf_to_text, search_filings, and ping (a single word but acceptable). No mixing of conventions or inconsistent styles.

Tool Count5/5

Seven tools is well-scoped for a Nordic financial data server. Each tool serves a necessary function without redundancy or bloat. The count covers core data retrieval, analysis, registry lookup, niche data (power prices), and utility tools (PDF parsing, health check), fitting the server's purpose.

Completeness4/5

The tool set covers the main workflows: searching filings, analyzing companies, retrieving registry data, fetching power prices, and extracting full documents. A minor gap is the lack of a direct Swedish registry lookup (get_company_info excludes Sweden, and search_filings doesn't provide registration data). Otherwise, the surface is well-rounded for Nordic financial queries.

Resources