Skip to main content
Glama

distributor_status

Lists configured distributors, shows API key presence and available services (parametric search, package, direct links), and gives setup steps for missing keys to help choose a distributor for a task.

Instructions

The distributors that datasheet-lens asks (from the project file, the global configuration or the default), if each has an API key (no key values), and the services of each distributor: which one has a parametric search, a package, direct links. Use it to select the distributor for a task. For a distributor with no key, a note with the steps for the user: give it to the user. The user changes the list with the CLI command "datasheet-lens dist NAME ..." (global) or "datasheet-lens dist --local NAME ..." (this project).

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": "distributor_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoA folder of the user project (default: the working folder of the server). The project file datasheet-lens.toml is in it or in a parent folder.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses the precedence of configuration sources (project file, global config, default), guarantees no key values are returned, and tells the agent to surface setup steps to the user when a key is missing. It does not say whether the tool performs any network probing of the distributors, which is a meaningful gap for an availability-style check.

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 payload is front-loaded but delivered as two long, comma-spliced sentences that mix return contents, agent instructions, and CLI syntax. Every piece of information is relevant, but the CLI instructions and the user-note directive would be far clearer as separate, shorter statements.

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?

An output schema exists, so return values need not be described, and the description still covers config-source precedence, key redaction, and per-distributor capabilities. The only missing piece is whether the check is purely local (config read) or involves live validation with distributors.

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% and the single path parameter is fully documented there, including the parent-folder lookup rule. The description's mention of 'the project file' corroborates the schema but adds no new parameter semantics, so the baseline 3 applies.

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 names a specific resource (distributors) and enumerates exactly what is reported: key presence without key values, and per-distributor services (parametric search, package, direct links). It is clearly distinct from the sibling search_distributors, though it never names that sibling to draw the contrast explicitly.

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

Usage Guidelines4/5

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

It states the selection condition directly: 'Use it to select the distributor for a task,' and explains how the list is configured and modified via the CLI. It stops short of explicitly pointing to search_distributors as the alternative once a distributor has been chosen.

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