fynk MCP

by com.fynk.app

Overview Discussions Admin

Get account info

get-account-info

Read-only

Get information about the current fynk account.

Use this tool when:

You need details about the active account (e.g. default document locale, signature settings) before tailoring a response
You are tailoring guidance to the account's business, and need what it reported about itself when signing up (industry, company size, the department the person who signed up works in)

For information about the current user, use get-user-info

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`name`	No
`locale`	No	Default account language, e.g. en-GB, de-AT. This language will be preselected for newly created documents/templates. fynk will generate AI summaries in this language. Prefer describing the locale in natural language (e.g. 'British English') rather than showing the raw code.
`status`	No	The account's subscription status. May fence access to certain app features
`created_at`	No	When the account was created
`_entity_type`	No	Only relevant for tooling. Do not show to the user
`sso_enforced`	No	If true, account users must authenticate via SSO rather than logging in with a password
`trial_ends_at`	No	If the account is in 'trial' status, when the trial ends and the account reverts to 'free'
`onboarding_profile`	No	What the account told us about its company when signing up. Self-reported and unverified - use it to tailor guidance, not as authoritative facts about the company. Fields that are not set are omitted
`default_comment_scope`	No	Controls the default visibility of comments and proposals in documents
`default_signature_type`	No	The default eIDAS assurance level to use when signing documents. May be overridden on individual documents
`finished_onboarding_at`	No	When the account completed the initial onboarding flow. Absent if onboarding has not yet been finished
`require_team_assignment`	No	When true, all documents, imports, and automations must have at least one team assigned
`auto_apply_ai_analysis_by_default`	No	When true, AI analysis results will be automatically applied when importing documents
`two_factor_authentication_enabled`	No	If true, users in the account must enable 2FA and use it when logging in
`require_template_for_document_creation`	No	When true, a template must be selected when creating a document from scratch or uploading a PDF to sign

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by enumerating what kind of data the account reports (locale, signature settings, industry, company size, department). It does not mention authentication or rate limits, but for a low-risk read-only tool this is a minor gap.

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 first sentence front-loads the purpose, followed by a tightly scoped bullet list of use cases and a final routing note. Every sentence earns its place, with no redundant explanation.

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?

An output schema exists, so the description need not explain return values. Combined with the clear purpose, usage conditions, sibling distinction, and zero-parameter schema, the definition gives the agent everything needed to invoke it correctly.

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 per the rubric the baseline is 4. The description correctly does not invent parameter semantics, and the empty schema is self-explanatory.

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 states a specific verb and resource: retrieving information about the current fynk account. It explicitly distinguishes itself from the sibling tool get-user-info, telling the agent exactly which resource each returns. An agent can select correctly without opening the schema.

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?

It provides explicit when-to-use conditions: before tailoring a response with account defaults, or when tailoring guidance using the account's self-reported business details. It also names the alternative (get-user-info) and the condition that selects it, leaving no routing ambiguity.

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

All fynk MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?