Skip to main content
Glama

Read plugin settings

AccountPluginSettingsReadTool
Read-onlyIdempotent

The account's plugin instances (plugin settings): list and inspect them, and read their data, logs, merge variables, a private plugin's files and the timeline of when each device shows them.

  • listPluginSettings: List my plugin settings — params: plugin_id (query)

  • getPluginSettingDetails: Get plugin setting details — params: id (path)

  • getPluginSettingData: Get the data of a native plugin setting; a private plugin reads through getMergeVariables — params: id (path)

  • getPluginSettingLogs: Read plugin instance health and recent logs — params: plugin_setting_id (path), level (query: one of debug, info, warn, error), limit (query)

  • getPluginSettingTimeline: Read a plugin setting timeline — params: plugin_setting_id (path), date (query)

  • getMergeVariables: Read the merge variables a plugin instance renders from — params: plugin_setting_id (path)

  • getPluginSettingFiles: Read the files of a private plugin — params: plugin_setting_id (path)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "AccountPluginSettingsReadTool"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesThe API operation to run
paramsNoThe operation's path, query and body parameters by name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered elsewhere. The description adds real value beyond that by characterizing what each sub-operation exposes — health/log levels, merge-variable rendering, private-plugin file access, and per-device timeline — which is not derivable from the annotations. It omits pagination behavior for listPluginSettings and any permission requirements for private-plugin file reads.

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?

Front-loaded opening sentence establishes scope, followed by a tight one-line-per-action enumeration with zero filler. The preamble is slightly run-on ('...and the timeline of when each device shows them') and could be trimmed, but each bullet earns its place.

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?

For a seven-action multiplexed tool with no output schema, the description is complete enough to route and invoke: every action has its parameters and a one-clause return characterization. Remaining gaps are around list pagination and the fact that getPluginSettingDetails uses 'id' while all sibling actions use 'plugin_setting_id', an inconsistency the description mirrors rather than explains.

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 schema documents only a generic 'params' object, so the description carries the real burden — and it does so per action, correctly tagging each parameter as path vs. query and expanding the level enum (debug, info, warn, error). It stops short of value formats: no date format for getPluginSettingTimeline, no default or range for limit.

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?

States a specific verb and resource ('list and inspect' the account's plugin instances) and then enumerates all seven sub-operations, so an agent knows exactly the surface area. It does not explicitly name AccountPluginSettingsWriteTool as the mutation counterpart, but the read-only framing plus the Read/Write sibling naming makes the split unambiguous.

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?

Each action is scoped to a distinct intent (list vs. details vs. data vs. logs vs. timeline vs. files), and the one genuinely ambiguous routing decision is resolved: 'a private plugin reads through getMergeVariables' tells the agent to prefer getMergeVariables over getPluginSettingData in that case. No explicit when-not or prerequisite guidance (e.g., required permissions) is given.

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