fmsg-mcp

Show fmsg identity

whoami

Read-onlyIdempotent

Report the fmsg address this server sends as, the Web API URL, short-name resolution, and server version; call first when unsure which identity is in use.

Instructions

Report the fmsg address this server acts as, the fmsg Web API URL and how short names resolve; the text also gives the server version. Call this first if unsure who you are sending as.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`address`	Yes
`api_url`	Yes
`transport`	Yes	one of "stdio", "http"; http is Streamable HTTP. More values may be added
`default_domain`	Yes
`directory_names`	Yes	short names in the operator-configured directory; empty when there are none
`token_expires_at`	Yes	internal: when the server's current upstream access token expires; it is renewed automatically, so no action is needed

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.1.0Oct 15, 2026

changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```

addedOutput schema / properties / directory_names / description

Added value: +"short names in the operator-configured directory; empty when there are none"

addedOutput schema / properties / token_expires_at / description

Added value: +"internal: when the server's current upstream access token expires; it is renewed automatically, so no action is needed"

addedOutput schema / properties / transport / description

Added value: +"one of \"stdio\", \"http\"; http is Streamable HTTP. More values may be added"

removedOutput schema / properties / transport / enum
```
Removed value: -[
-  "stdio",
-  "http"
-]
```

Changed1 schema field changedv0.2.3Sep 25, 2026
- changedOutput schema / properties / api_url / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
First observedv0.1.3Sep 5, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description restates what is returned (address, API URL, version) but that content is also covered by the existing output schema, so it adds little behavioral context about auth, failures, or limits.

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?

Two short sentences, identity scope front-loaded and the invocation hint placed last where it is easy to act on. The semicolon clause is slightly dense but nothing is wasted.

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?

For a no-arg, read-only diagnostic tool with an output schema, the description supplies purpose, return contents at a summary level, and a when-to-call trigger. Nothing an agent needs to invoke it correctly is missing.

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 schema semantics are a non-issue and the baseline is 4. There is nothing for the description to disambiguate.

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

Purpose4/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 set: reports the fmsg address the server acts as, the Web API URL, short-name resolution, and server version. That is far more precise than the title 'Show fmsg identity'. It does not explicitly contrast itself with resolve_address, which is the nearest sibling, so it stops short of a 5.

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?

"Call this first if unsure who you are sending as" gives a concrete trigger condition, which is unusual and useful. It does not state when NOT to call it or name resolve_address as the alternative for name lookups, so it is clear context without full routing guidance.

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

Deploy Server