Skip to main content
Glama

Importer Session

importer_session

Imports a session from Firefox or Epiphany and verifies it, providing a fallback when the primary session source is unavailable.

Instructions

Repli : importe la session depuis Firefox ou Epiphany, puis la vérifie.

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": "importer_session"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose a genuine two-stage behavior (import, then verify) and names the two supported browsers. However, it omits the things that matter for an import operation: whether an existing session is overwritten, whether the browser must be closed, permission/auth requirements, and what 'vérifie' actually checks. Useful but incomplete behavioral context.

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?

A single short sentence that front-loads the fallback framing and then the action. Nothing is padded. The only cost is that the terseness leaves key terms ('Repli', 'vérifie') unexplained.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and there are no parameters to document. What is missing is the operational context an agent would need before invoking a session-import: side effects on existing session state, failure modes when a browser is absent or locked, and what the verification step guarantees.

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 there is nothing for the description to disambiguate; baseline for a 0-param tool is 4. The one implicit choice (which browser to import from) is at least surfaced in prose, though it is not presented as a selectable option.

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 gives a concrete verb and resource ('importe la session') plus the source systems ('depuis Firefox ou Epiphany') and a follow-up step ('puis la vérifie'). That is far more specific than the bare name 'importer_session'. The unexplained 'Repli :' prefix and the absence of any explicit contrast with siblings keep it from a 5, though the sibling catalog (all sondage/calendrier tools) makes confusion unlikely.

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

Usage Guidelines2/5

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

'Repli' hints that this is a fallback path, but the description never says what it is a fallback *to*, nor when the agent should prefer it over other session or connection tools (e.g. 'ouvrir_connexion'). No prerequisites, no exclusions, no stated conditions are given.

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