Skip to main content
Glama
Sign In
easy-equities-mcp

easy-equities-mcp

by heinrich321
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

refresh_session

Re-authenticate a session using stored credentials when cookies expire. Call this to force a fresh login without passing credentials through chat.

Instructions

Re-authenticate one session using credentials from the environment/.env.

Call this from chat when a tool call fails because cookies have expired or to force a fresh login. Credentials are never passed through chat.

Args: session: The session name, e.g. "personal".

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session": "<session>"
    },
    "name": "refresh_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden. It discloses that credentials come from the environment and are not passed via chat, and that the operation re-authenticates (a mutating action). It doesn't detail side effects or failure behavior, but provides meaningful security context beyond the schema.

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 concise with a clear opening statement, usage context, and a simple args list. Every sentence contributes value, with no waste.

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?

The tool is simple (single param) and has an output schema, so return values are covered. The description covers purpose, when to use, and parameter semantics. It doesn't mention error cases, but for a focused refresh operation this is adequate.

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?

Schema coverage is 0%, so the description must compensate. It explains that the session parameter is the session name and gives an example ('personal'), which adds meaning not present in the bare schema.

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 tool re-authenticates a single session using environment/.env credentials. It distinguishes from refresh_all_sessions by specifying 'one session' and names the action as re-authentication.

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?

Explicitly states when to use: when a tool call fails due to expired cookies or to force a fresh login. It also notes that credentials are never passed through chat, guiding secure usage. The alternative refresh_all_sessions is implied by contrast.

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

Deploy Server

Other Tools