Skip to main content
Glama

get_connection_status

get_connection_status
Read-onlyIdempotent

Check whether this request is connected to a TalkJS test app. No login is required. When disconnected, returns concrete login instructions to show the user for their client.

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_connection_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real value beyond them: it discloses that authentication is not needed and, importantly, that the disconnected branch returns concrete login instructions intended for display to the user. The connected-branch return value is left implicit.

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?

Three short sentences, each earning its place: purpose first, auth precondition second, result-handling third. No redundant wording and no repetition of the tool name or title.

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?

With no output schema, the description carries the burden of explaining returns; it covers the disconnected case well but only implies the connected case (a status/affirmative result). For a trivial zero-parameter probe with full annotation coverage, this is nearly complete but leaves one branch underspecified.

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 no parameter semantics to explain; the schema is empty and fully described. Baseline for a no-parameter tool is 4, and nothing in the description conflicts with the 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 opens with a specific verb and resource: 'Check whether this request is connected to a TalkJS test app.' That states exactly what the tool returns and scopes it to connection status, which is plainly distinct from the sibling tools (secret key CRUD and settings management). An agent can identify this tool's role without opening the schema.

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

Usage Guidelines4/5

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

It gives clear operating context ('No login is required') and tells the agent what to do with a negative result: show the returned login instructions to the user's client. What's missing is an explicit statement of when to call it relative to the sibling tools (e.g., before attempting authenticated operations), though for a zero-param status probe the implicit usage is fairly obvious.

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