Skip to main content
Glama
LerianStudio

Lerian MCP Server

by LerianStudio
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

lerian

Read-onlyIdempotent

Explore docs, tutorials, SDK examples, and portfolio search for Midaz, Reporter, Fetcher, Matcher, Tracer, Flowker, Underwriter. Discover MCP coverage and generate code for your use case.

Instructions

Unified portfolio tool for Lerian products. Discover supported products and current MCP coverage, access documentation and learning resources, generate SDK examples, and search across the portfolio. Live API execution is available through product-specific tools for Midaz, Fetcher, Reporter, Matcher, Tracer, Flowker, and Underwriter, with cross-product workflow support available via portfolio-workflow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNoTopic or subject matter, 5-200 characters (REQUIRED for: docs, learn, search). Examples: 'getting-started', 'authentication', 'transactions', 'templates', 'rules', 'workflows'. Be specific about what you want to learn or find.
formatNoResponse detail level. 'summary': brief overview (~200 chars), 'detailed': comprehensive with examples, 'examples-only': code samples only. Default: 'detailed'.detailed
productYesTarget Lerian product (REQUIRED). Use 'all' for portfolio-wide discovery and search. Supported products: midaz, reporter, fetcher, matcher, tracer, underwriter, flowker, all.
useCaseNoSpecific use case for SDK code generation, 10-200 characters (REQUIRED for: sdk operation). Examples: 'create first transaction', 'setup authentication', 'handle errors', 'build workflow', 'generate report'. Be specific about implementation scenario.
languageNoProgramming language (REQUIRED for: sdk operation). 'go': backend services, high performance, 'typescript': type-safe development, 'javascript': Node.js and web. Check product.sdkLanguages for available options.
operationYesOperation type (REQUIRED). 'discover': inspect portfolio products and current MCP coverage, 'docs': get documentation, 'learn': interactive tutorials and learning paths, 'sdk': generate SDK code, 'search': search documentation and examples.
maxResultsNoMaximum search results to return (for: search operation). Range: 1-50, default: 10. Use lower numbers (1-5) for focused results, higher (10-20) for exploration.
experienceLevelNoYour experience level with the product (for: learn operation). 'beginner': new to product, 'intermediate': basic understanding, 'advanced': production experience. Affects tutorial depth and complexity.beginner
includeExamplesNoInclude code examples in documentation responses. Default: true. Set false for text-only documentation.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed6 schema fields changedv3.7.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / operation / description
      Previous value: -"Operation type (REQUIRED). 'docs': get documentation, 'learn': interactive tutorials and learning paths, 'sdk': generate SDK code, 'search': search documentation and examples."New value: +"Operation type (REQUIRED). 'discover': inspect portfolio products and current MCP coverage, 'docs': get documentation, 'learn': interactive tutorials and learning paths, 'sdk': generate SDK code, 'search': search documentation and examples."
    • changedInput schema / properties / operation / enum
      Previous value: -[
-  "docs",
-  "learn",
-  "sdk",
-  "search"
-]New value: +[
+  "discover",
+  "docs",
+  "learn",
+  "sdk",
+  "search"
+]
    • changedInput schema / properties / product / description
      Previous value: -"Target Lerian product (REQUIRED). 'midaz': financial ledger, 'tracer': observability, 'flowker': workflows, 'reporter': analytics, 'all': search across all products."New value: +"Target Lerian product (REQUIRED). Use 'all' for portfolio-wide discovery and search. Supported products: midaz, reporter, fetcher, matcher, tracer, underwriter, flowker, all."
    • changedInput schema / properties / product / enum
      Previous value: -[
-  "midaz",
-  "tracer",
-  "flowker",
-  "reporter",
-  "all"
-]New value: +[
+  "midaz",
+  "reporter",
+  "fetcher",
+  "matcher",
+  "tracer",
+  "underwriter",
+  "flowker",
+  "all"
+]
    • changedInput schema / properties / topic / description
      Previous value: -"Topic or subject matter, 5-200 characters (REQUIRED for: docs, learn, search). Examples: 'getting-started', 'authentication', 'transactions', 'error-handling', 'workflows'. Be specific about what you want to learn or find."New value: +"Topic or subject matter, 5-200 characters (REQUIRED for: docs, learn, search). Examples: 'getting-started', 'authentication', 'transactions', 'templates', 'rules', 'workflows'. Be specific about what you want to learn or find."
  2. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

The description aligns with the readOnlyHint annotation by noting that live execution is available elsewhere, but it adds little beyond that. It does not discuss potential errors, required authentication, or output behavior, so transparency is moderate given annotations already cover read-only and idempotency.

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?

The description is moderately concise and front-loaded with the core purpose ('Unified portfolio tool'), then lists functions and alternatives. It avoids redundancy but could be trimmed slightly, such as removing the full list of product names that are also in the schema enum.

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?

Provides enough context to understand the tool's role and boundaries (e.g., no live execution, pointing to siblings). It does not describe return values or detailed behavior, but given the schema richness and explicit sibling references, the agent is likely to use it correctly. Missing output format description is a minor gap.

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?

The description adds minimal parameter context beyond what the schema already provides. While it restates the tool's operations, the schema descriptions already explain each parameter's use, required conditions, and enums, so the added semantic value is low.

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 identifies the tool as a unified portfolio interface for Lerian products, enumerating specific functions (discover, docs, generate SDK, search) and explicitly naming sibling tools for live API execution, which distinguishes its purpose from those alternatives.

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

Usage Guidelines4/5

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

Provides explicit guidance that live API execution should be done via product-specific tools and cross-product workflows via 'portfolio-workflow', helping the agent choose when to use this tool versus siblings. It does not elaborate on contextual prerequisites or when to pick one operation over another in detail.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/LerianStudio/lerian-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server