fynk MCP

by com.fynk.app

Overview Discussions Admin

Get user info

get-user-info

Read-onlyIdempotent

Get information about the current user.

Use this tool when:

You need to know who the current user is (email, locale, roles) before tailoring a response

For information about the current fynk account, use get-account-info

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-user-info"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`email`	No
`roles`	No	The roles the user has in the current account
`locale`	No	Code for the user's selected locale, e.g. en-GB, de-AT. Prefer describing the locale in natural language (e.g. \'British English\') rather than showing the raw code.
`_entity_type`	No	Only relevant for tooling. Do not show to the user
`current_account`	No	The fynk account that the user is currently logged in to
`current_account_user`	No	Details about the user that are specific to the fynk account they are currently logged in to

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 10, 2026

addedOutput schema / properties / current_account_user / properties / first_name

Added value: +{
+  "description": "User's first name. Absent when the user has none set",
+  "type": "string"
+}

addedOutput schema / properties / current_account_user / properties / last_name

Added value: +{
+  "description": "User's last name. Absent when the user has none set",
+  "type": "string"
+}

First observedOct 20, 2026

TDQS

A4.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-open-world and non-destructive, so the safety profile is covered. The description adds little beyond that—it names the fields surfaced, but says nothing about permissions, staleness of data, or behavior if no session exists; an output schema also exists, so field enumeration is partly redundant. Adequate but not rich.

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?

Front-loaded opening sentence followed by a single tightly scoped bullet and a routing sentence. Minor overhead from the bullet list formatting for what is essentially one condition, but no sentence is wasted.

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?

A parameterless, read-only lookup with annotations and an output schema in place—everything the agent needs to decide to call it and what it will receive is present in the description plus structured fields.

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 is 4; there is nothing for the description to disambiguate, and it correctly doesn't invent inputs.

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?

States a specific verb and resource ('Get information about the current user') and enumerates the returned fields (email, locale, roles), which lets an agent distinguish it from get-account-info immediately.

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?

Explicit 'Use this tool when' condition plus an explicit alternative for the adjacent case ('For information about the current fynk account, use get-account-info'), which is exactly the when/when-not pattern.

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?