Skip to main content
Glama

get_settings

get_settings
Read-onlyIdempotent

Read basic settings for the connected TalkJS test app. Requires login and settings:read. If authentication is required, show the user the concrete steps for their client: Connect your TalkJS account using the steps for your client:

  • Codex CLI: type /mcp login talkjs in the active Codex session.

  • Claude Code: type /mcp, select the TalkJS server, and follow the authentication prompts.

  • ChatGPT web: use the Connect/Sign in prompt shown for the TalkJS tool. If no prompt appears, open the TalkJS plugin's connection settings and connect your account.

  • Claude web: open Customize > Connectors, find TalkJS, and click Connect.

  • Cursor: open Customize > MCP, select TalkJS, and follow the sign-in prompt.

  • Other MCP clients: open the TalkJS server's connection settings and choose Authenticate, Sign in, or Connect.

talkjs in these commands is the configured MCP server name. Substitute the actual name if it was registered differently. Complete browser authorization, choose the TalkJS project's test app, then retry the requested operation.

Terminal alternatives: run codex mcp login talkjs for Codex or claude mcp login talkjs for Claude Code. After terminal login, reconnect the MCP server in the active client if it still reports disconnected; start a new agent session if necessary.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds useful behavioral context by disclosing the authentication and settings:read permission requirements, plus what to do if authentication is needed. It does not describe the returned settings in detail, but the annotations carry much of the safety profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are concise and front-load the tool purpose and permission requirement. The remaining bulk consists of lengthy generic authentication instructions across multiple clients, terminal alternatives, and retry guidance, which is disproportionate for a zero-parameter read tool and obscures the core definition.

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 description covers authentication and permission requirements well, which is relevant for this tool. However, it does not explain what 'basic settings' includes, and there is no output schema to document the return values, leaving some uncertainty about what the tool provides.

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 input parameters, so there are no parameter semantics that the description needs to clarify. With no parameters and an empty schema, the baseline score is appropriate.

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 clearly states a specific verb and resource: read basic settings for the connected TalkJS test app. It does not explicitly contrast this with update_settings or other sibling tools, but the read-only scope is clear from the verb and resource.

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 this is the tool for reading app settings and states the login and settings:read prerequisites. However, it does not provide explicit guidance on when to use this tool versus related tools such as get_connection_status or update_settings.

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