Skip to main content
Glama

BraFinder

by io.github.fenrici1

translate_bra_size

Translate a bra size across brands. Give a size (e.g. "34DD"), optionally the brand it is from, and optionally a single target brand. Returns the equivalent size in the target brand, or in every brand if no target is given, each with a fit note and confidence. Bra brands do NOT use the same sizing; this is the neutral cross-brand translation. Use for "what size am I in [brand]", "is a 34DD the same in [brand A] and [brand B]", "convert my size to [brand]".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeYesA bra size like "34DD", "32F", "36C".
to_brandNoA single target brand (optional). Omit to translate to every brand.
from_brandNoThe brand the size is from (optional). Omit to treat it as a standard US size.

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It discloses that output includes equivalent size with fit note and confidence, and that omitting to_brand returns all brands. No side effects or destructive actions expected, making this adequate.

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 with key information front-loaded: verb, constraints, and use cases. Every sentence is necessary and efficiently written.

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 tool with 3 parameters and no output schema, the description covers all critical aspects: what it does, parameter semantics, output content, and usage scenarios. Sibling tools provide additional context.

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

Parameters4/5

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

Schema coverage is 100%, but description adds value by explaining optional behavior (to_brand: omit for all brands; from_brand: omit treats as US standard). Examples further clarify parameter usage.

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 clearly states the verb ('Translate') and resource ('bra size'), and explicitly distinguishes from sibling tools by specifying cross-brand translation. Examples like 'what size am I in [brand]' solidify purpose.

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?

Provides explicit use cases ('Use for...') and explains the non-equivalence of sizes across brands. Does not explicitly state when not to use, but the context is clear enough for an agent to infer.

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

All BraFinder toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Tools are mostly distinct: bra_brand_fit gives fit notes, translate_bra_size gives exact conversions, find_bras finds products, bra_size_dataset provides raw data. However, bra_brand_fit and translate_bra_size both deal with cross-brand sizing, which could cause minor confusion.

Naming Consistency3/5

Naming patterns are mixed: 'find_bras' and 'translate_bra_size' follow verb_noun, while 'bra_brand_fit' and 'bra_size_dataset' are noun phrases starting with 'bra'. Inconsistent but still clear.

Tool Count4/5

4 tools is reasonable for a niche domain like bra sizing. Not overly thin, covers key operations without excess. Could add one more tool for user contributions, but current count is appropriate.

Completeness4/5

Covers core use cases: finding fit notes, translating sizes, searching bras, and accessing the dataset. Missing update/delete operations, but this is a read-only informative server, so gaps are minor.

Resources