Skip to main content
Glama
Sign In
Databar MCP Server

Databar MCP Server

Official
by databar-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_exporter_details

Retrieve detailed information about an exporter, including required parameters and output fields, to prepare for adding it to a table.

Instructions

Get detailed information about a specific exporter, including its required parameters and output fields. Use this to understand what parameters are needed before adding the exporter to a table.

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": {
      "exporter_id": "<exporter_id>"
    },
    "name": "get_exporter_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
exporter_idYesThe exporter ID (from search_exporters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden. It only mentions what the tool returns (parameters and output fields) but does not disclose any behavioral aspects like authentication, rate limits, or side effects. As a read operation, this is acceptable but lacking.

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?

Two sentences efficiently convey purpose and usage. No redundant words; front-loaded with the main action and scope.

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 tool with one parameter and no output schema, the description adequately explains what it returns and why to use it. It could be more complete by specifying the format of the returned details, but it is sufficient for the context.

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 parameter 'exporter_id' has a clear description in the schema ('The exporter ID (from search_exporters)'). The description adds no additional meaning beyond the schema, so the baseline of 3 is appropriate given 100% schema coverage.

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?

The description clearly states the tool's action ('get detailed information') and resource ('specific exporter'), including contents ('required parameters and output fields'). It is distinct from sibling tools like 'get_table_exporters' and 'search_exporters' by focusing on a single exporter by ID, but does not explicitly differentiate.

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 provides a specific use case ('before adding the exporter to a table'), implying when to use it. However, it offers no guidance on when not to use it or alternatives, leaving the agent to infer context.

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