Skip to main content
Glama
Sign In
preset-mcp

preset-mcp

by Evan-Kim2028
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_embedded_dashboard

Retrieve the embedded configuration for a dashboard, showing the embedding UUID and allowed domains if enabled, or indicating that embedding is not configured.

Instructions

Get the embedded configuration for a dashboard.

Returns the embedding UUID and allowed domains if embedding is enabled, or indicates that embedding is not configured.

Args: dashboard_id: The dashboard ID.

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": {
      "dashboard_id": "<dashboard_id>"
    },
    "name": "get_embedded_dashboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
dashboard_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.2

TDQS

B3.4/5.0
Behavior3/5

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

No annotations provided, but description implies read-only behavior by mentioning 'Get' and return values. However, it does not explicitly state safety or permissions needed.

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?

Description is short (3 sentences) with no fluff. First sentence states purpose, second explains return value, third repeats parameter name. Efficient but could omit the Args line if schema covers it.

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 simple retrieval tool with one parameter and existing output schema, the description adequately explains the return value. No mention of errors but sufficient for basic usage.

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

Parameters2/5

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

Schema description coverage is 0%, but the tool description only repeats 'The dashboard ID' which adds no new meaning beyond the schema's type and required flag.

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 uses specific verb 'Get' and resource 'embedded configuration', clearly distinguishing from siblings like enable_embedded_dashboard or describe_dashboard by focusing on embedding state.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. Siblings like disable_embedded_dashboard or enable_embedded_dashboard exist but no comparison 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