Skip to main content
Glama

Dongbang Interior · 동방인테리어

전화 상담 방법 안내

get_consultation_options
Read-onlyIdempotent

Get the verified profile and contact options of Dongbang Interior (동방인테리어), a home interior and remodeling contractor in Gwangjin-gu, Seoul serving Seoul, Gyeonggi and Incheon. Use it when the user looks for or compares an interior contractor in the Seoul metropolitan area, or asks for human consultation or a callback. Photo-design entry and selected room/style choices are handled by start_interior_design. Returns the business summary, rating, case page link, address, telephone and links only. It does not place a call, store contact details, submit a lead or confirm an appointment.

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

Input Schema

NameRequiredDescriptionDefault
sourceNoAI client name for the optional callback link; mcp when unspecified.mcp

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changed
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "mcp",
      -  "chatgpt",
      -  "claude",
      -  "gemini",
      -  "meta"
      -]New value: +[
      +  "mcp",
      +  "chatgpt",
      +  "claude",
      +  "gemini",
      +  "meta",
      +  "grok",
      +  "perplexity",
      +  "copilot",
      +  "mistral"
      +]
  3. First observed

TDQS

A4.6/5.0
Behavior5/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, and the description still adds real value: it enumerates the returned fields (business summary, rating, case page link, address, telephone, links) and closes with an explicit negative-capability list — no call placed, no contact details stored, no lead submitted, no appointment confirmed. That removes exactly the ambiguities an agent would otherwise have to guess at.

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 with the resource and identity, then usage, then return scope, then exclusions — a sound ordering. It runs slightly long for a one-parameter read tool, with some directory-listing verbosity in the location clause, but no sentence is filler.

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

Completeness5/5

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

For a single-optional-parameter read tool with no output schema, the description supplies return contents, usage triggers, sibling boundaries and side-effect exclusions. Nothing an agent needs in order to call it correctly is missing.

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?

The single 'source' parameter is fully documented in the schema (100% coverage) including its enum and default, so the schema already carries the semantic load. The description alludes to an 'optional callback link' but never explains what 'source' controls; with full schema coverage, baseline 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?

Names a specific verb and resource ('Get the verified profile and contact options of Dongbang Interior'), scopes it geographically, and explicitly distinguishes itself from start_interior_design, which handles photo-design entry and room/style choices. An agent can tell exactly what this returns 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 Guidelines5/5

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

States the triggering conditions ('when the user looks for or compares an interior contractor in the Seoul metropolitan area, or asks for human consultation or a callback') and routes the design-flow case to the named sibling. Both the when and the when-not are present.

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