Skip to main content
Glama
TylerFlar

claude-fidelity-mcp

by TylerFlar

fidelity_status

Check whether your Fidelity browser session is active and logged in. Verifies authentication status to ensure secure access to account management.

Instructions

Check whether the Fidelity browser session is active and logged in.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the 'fidelity_status' tool. Checks if the Fidelity browser session is active and logged in by calling isBrowserReady(), then returns a JSON response with browserActive and a contextual message.
    server.tool(
      "fidelity_status",
      "Check whether the Fidelity browser session is active and logged in.",
      {},
      async () => {
        const ready = isBrowserReady();
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(
                {
                  browserActive: ready,
                  message: ready
                    ? "Browser session is active. You can use Fidelity tools."
                    : "No active session. Use fidelity_login to start.",
                },
                null,
                2
              ),
            },
          ],
        };
      }
    );
  • src/index.ts:398-424 (registration)
    Registration of the 'fidelity_status' tool on the MCP server via server.tool(). Includes a description and an empty schema object (no parameters).
    // ─── Status ─────────────────────────────────────────────────────────────────────
    
    server.tool(
      "fidelity_status",
      "Check whether the Fidelity browser session is active and logged in.",
      {},
      async () => {
        const ready = isBrowserReady();
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(
                {
                  browserActive: ready,
                  message: ready
                    ? "Browser session is active. You can use Fidelity tools."
                    : "No active session. Use fidelity_login to start.",
                },
                null,
                2
              ),
            },
          ],
        };
      }
    );
  • Helper function isBrowserReady() that returns true if a Page object exists and is not closed. Used by the fidelity_status handler to determine session status.
    export function isBrowserReady(): boolean {
      return page !== null && !page.isClosed();
    }
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It states the tool checks session activity, but does not specify what constitutes 'active' or 'logged in', nor how the result is returned (boolean, status string, etc.). Minimal behavioral detail.

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 description is a single concise sentence of 8 words with no redundancy. Every word is necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no output schema, so the description should clarify the return value format. It only says 'Check whether', which is ambiguous about output (e.g., boolean, string). Missing return details make it incomplete for an agent.

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?

There are zero parameters, so the schema provides no information. The description adds the meaning of the tool's action, which is sufficient for a parameterless tool. Baseline for 0 params is 4.

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 verb 'Check whether' and the resource 'Fidelity browser session is active and logged in', distinguishing it from sibling tools like fidelity_login or fidelity_logout which perform different actions.

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

Usage Guidelines3/5

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

The description gives no explicit guidance on when to use this tool vs alternatives. Usage is implied (checking session status before other operations), but no when-not-to-use or alternatives are mentioned.

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/TylerFlar/claude-fidelity-mcp'

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