Skip to main content
Glama
Sign In
wiswa-mcp

wiswa-mcp

by Tatsh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

lookup_setting

Look up a setting by dot-separated key path to get its default value and override snippet.

Instructions

Look up a setting by dot-separated key path and get its default value plus override snippet.

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": {
      "key_path": "<key_path>"
    },
    "name": "lookup_setting"
  }
}

Input Schema

NameRequiredDescriptionDefault
key_pathYesDot-separated path to the setting.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

A3.8/5.0
Behavior3/5

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

The description discloses that the tool returns 'default value plus override snippet', which is helpful. However, with no annotations, it does not address error behavior (e.g., missing key), side effects, or permissions. The safety profile is implied as a read operation but not explicitly stated.

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, clear sentence with no unnecessary words. It efficiently conveys the core functionality.

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?

Given the tool's simplicity (one parameter, output schema exists), the description adequately covers the return values. It does not specify error handling or edge cases, but for a straightforward lookup, it is largely complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with 'key_path' described. The description repeats 'dot-separated key path' without adding new meaning. Since coverage is high, baseline score of 3 applies.

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 clearly states the tool's purpose: to look up a setting by dot-separated key path and return its default value and override snippet. It distinguishes this from sibling tools (get_defaults, list_settings, search_settings) by specifying exact path lookup.

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 when the exact key path is known, but does not explicitly state when to use this tool over siblings like get_defaults or search_settings. No when-not or alternative guidance is provided.

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