Skip to main content
Glama

Get the current setting

get_setting

Retrieve the current configuration for the virtual travel environment on Google Maps, enabling users to manage avatar journeys and photo reports effectively.

Instructions

Get current setting

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_setting' tool. It fetches the system version and environment settings from the database, formats them into a textual summary, and returns it as a tool content response.
    const getSetting = () => {
      return Effect.gen(function* () {
        const version = yield* DbService.getVersion()
        const runnerEnv = yield *DbService.getSysEnv()
        const envText = 'A json of current environment settings\n' +
          Object.entries(runnerEnv.mode).map(([key, value]) => {
            return `${key}= ${JSON.stringify(value)}`
          }).join('\n') +
          '\nList of Image settings\n' +
          (runnerEnv.bodyAreaRatio ? `bodyAreaRatio=${runnerEnv.bodyAreaRatio}\n` : '') +
          (runnerEnv.bodyHWRatio ? `bodyHWRatio=${runnerEnv.bodyHWRatio}\n` : '') +
          (runnerEnv.bodyWindowRatioW ? `bodyWindowRatioW=${runnerEnv.bodyWindowRatioW}\n` : '') +
          (runnerEnv.bodyWindowRatioH ? `bodyWindowRatioH=${runnerEnv.bodyWindowRatioH}\n` : '') +
          (runnerEnv.noImageOut ? `noImage=true\n` : '') +
          (runnerEnv.isEnableFeedTag ? `feedTag=${runnerEnv.extfeedTag}\n` : '') +
          `version=${version}\n`
        return [{
          type: "text",
          text: envText
        } as ToolContentResponse]
      })
    }
  • Registration of the 'get_setting' tool in the SETTING_COMMANDS array, including name, title, description, and input schema (empty object). This is part of the tools list provided to the MCP server.
    {
      name: "get_setting",  //  pythonがあったらよいとか、db設定がよいとか、tipsを取得する。tipsの取得を行うのはproject側スクリプトとか、script batchとか
      title: "Get the current setting",
      description: "Get current setting",
      inputSchema: {
        type: "object",
        properties: {}
      }
    },
  • Dispatch case in the toolSwitch function that routes calls to the 'get_setting' tool to the getSetting handler.
    case "get_setting":
      return getSetting()
  • Export of the getSetting function as part of the McpService class methods.
    getSetting,
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. However, it offers no information about traits such as whether this is a read-only operation, if it requires authentication, potential rate limits, or what the return format might be. This is inadequate for a tool with no annotation coverage.

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

Conciseness3/5

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

The description is extremely concise ('Get current setting'), which could be seen as efficient. However, it's under-specified rather than appropriately sized, failing to provide necessary context. It's front-loaded but lacks substance, making it borderline between conciseness and insufficiency.

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

Completeness1/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'setting' refers to, what data is returned, or how this tool fits into the context of sibling tools (e.g., traveler-related operations). For a tool with no structured data support, the description fails to provide essential context.

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 0 parameters, and the schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it doesn't introduce any confusion. A baseline score of 4 is appropriate as the schema fully handles the parameter aspect.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get current setting' is a tautology that merely restates the tool name and title without adding specificity. It doesn't clarify what type of setting (e.g., system, user, application) or which resource it retrieves, nor does it distinguish this tool from its siblings like 'get_traveler_info' or 'get_traveler_location'.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any context, prerequisites, or exclusions, leaving the agent with no information to decide between this tool and sibling tools like 'get_traveler_info' or 'set_traveler_info'.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mfukushim/map-traveler-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server