Skip to main content
Glama
Sign In
datasheet-lens

datasheet-lens

by turbyho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_price_locale

Sets the country and currency for price and stock data in the global configuration, so DigiKey results reflect the chosen locale; change only when the user requests it.

Instructions

Set the country and the currency of the prices and the stock of DigiKey in the global configuration of the user, as the CLI command "datasheet-lens dist --site CZ --currency CZK". Mouser uses the country of the Mouser account, and JLCPCB gives USD. Give one of the two or the two. Change it only when the user asks.

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

Input Schema

NameRequiredDescriptionDefault
siteNoThe country of the prices and the stock: a code of 2 letters, for example CZ, DE or US. Empty: no change.
currencyNoThe currency of the prices: a code of 3 letters, for example CZK, EUR or USD. Empty: no change.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0

TDQS

A3.8/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does disclose substantive behavior: the change is persistent ('global configuration of the user'), scoped to DigiKey pricing/stock only, and publicly discouraged absent an explicit user request. Gaps remain around validation (invalid codes), whether a confirmation or prior state is returned, and whether other tools read this setting.

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 operative instruction is front-loaded, but the middle sentences about Mouser, JLCPCB, and the exact CLI invocation are digressive, and 'Give one of the two or the two' is awkward phrasing that takes effort to parse. It is not wasteful overall, but the structure could be tighter.

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 no explanation, and the description covers persistence, scope, and the user-consent condition for a two-optional-parameter mutation tool. It does not mention failure modes for invalid country or currency codes, which is the main remaining gap.

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 both parameter descriptions already state the format (2-letter site, 3-letter currency) and the 'empty means no change' semantics. The description's 'Give one of the two or the two' adds a small amount of meaning about partial updates, but largely restates the schema, so the baseline of 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?

States a specific verb and resource: it sets the country (site) and currency used for DigiKey prices and stock in the user's global configuration. It further clarifies which distributors are NOT affected (Mouser uses the account country, JLCPCB gives USD), which sharpens the scope. It loses a point only because the CLI example and distributor asides slightly obscure the single sentence an agent needs.

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?

Explicitly constrains when to call it: 'Change it only when the user asks.' It also implies when it is irrelevant by naming distributors whose pricing is unaffected. There is no named sibling alternative for locale-related work, but no such sibling exists in the tool list, so the guidance is near-complete.

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