Skip to main content
Glama

Qui Suis Je

qui_suis_je
Read-only

Retrieves the active session and connected account details to diagnose authentication or identity issues in Evento.

Instructions

Session utilisée et compte connecté (diagnostic).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so credit goes only for added context. "Session utilisée" usefully implies the tool reflects the *current* session rather than an arbitrary one, which is genuine behavioral information. It still says nothing about what happens when unauthenticated or what identity is assumed, leaving gaps typical of a diagnostic.

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?

Six words, front-loaded, no waste. The only cost is that the elliptical fragment style (no verb) makes the sentence slightly cryptic out of context.

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 described, and the tool is parameterless and read-only, keeping complexity low. Still, for a diagnostic whose whole value is telling the agent who it is acting as, one clause on failure modes (no valid session, expired token) would round it out.

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 and the schema is empty with additionalProperties=false, so there is no parameter meaning to convey. The baseline for a parameterless tool applies.

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

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resources involved ("Session utilisée" and "compte connecté") and tags the tool as "diagnostic", which distinguishes it from the survey/calendar siblings. However it is a noun phrase with no verb, so it never explicitly states that the tool *returns* or *reports* that information — the agent must infer the operation.

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?

"(diagnostic)" hints at the use case, but there is no explicit statement of when to call this versus the other tools, and no prerequisites mentioned. With 23 siblings and zero guidance, the agent has to guess that this is a connectivity/auth self-check.

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