Skip to main content
Glama

Who am I in docket

get_context
Read-onlyIdempotent

Returns the connected user (name, role, default service), the workspace, its country and the currency its amounts are in, today's date and time zone, and what this connection may do.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description doesn't need to restate it. It adds genuine value by disclosing exactly which context fields come back, including permission scope ('what this connection may do'), which matters for an agent deciding what it may attempt next.

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?

A single dense sentence with zero filler, front-loading the primary return value (the connected user) before the secondary context fields. Every clause enumerates a distinct returned datum.

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

Completeness5/5

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

There is no output schema, so the description carries the full burden of describing return values – and it does so completely and specifically, covering identity, workspace, locale/currency, temporal context, and permissions. Nothing an agent needs before calling is missing.

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?

Zero parameters, so the baseline of 4 applies; the description correctly adds no parameter noise and the empty schema leaves nothing undocumented.

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?

A specific verb ('Returns') with a precisely enumerated resource: connected user identity, workspace, country, currency, date/time zone, and permission scope. No sibling tool covers identity/context, so an agent can immediately tell this apart from the ticket, time-entry, and financial tools.

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?

Usage is implied rather than stated – the content list makes it obvious this is the 'orient yourself before acting' call, and 'what this connection may do' hints at permission checks. However, there is no explicit 'call this first' directive, no when-not-to-use condition, and no reference to any sibling.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources