Skip to main content
Glama
Sign In
TaskLogger MCP

TaskLogger MCP

by khodorrrhajjj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

status

Verify your authentication status and identify the logged-in user. Returns current user details or indicates unauthenticated state.

Instructions

Check if authenticated and which user is logged in.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description must carry full behavioral disclosure. It states the purpose but does not explicitly disclose side effects, return format, error behavior if unauthenticated, or whether it is a read-only operation. The verb 'Check' hints at safety but does not confirm it.

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, front-loaded sentence that directly states the tool's purpose. There is no wasted text, and it is appropriately concise for a tool with no parameters.

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?

The tool is simple (zero parameters, no output schema), and the description covers the core function. However, it lacks details about the response structure (e.g., whether it returns a boolean or user object) and any edge-case behavior such as what happens when not authenticated. More explicit return information would make it more complete.

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 has zero parameters, so the schema fully covers parameter semantics. The baseline for 0-param tools is 4, and the description does not need to explain anything further since there is nothing to explain.

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 uses a specific verb ('Check') and clearly identifies the resource (authentication status and current user). It distinguishes itself from sibling tools like login and logout by focusing on status inspection rather than auth changes.

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 implies usage: it is the tool to call when you need to know if the user is authenticated and who they are. However, it does not explicitly state when to use this versus alternatives, nor does it provide exclusions or mention that login/logout cover auth changes.

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