Skip to main content
Glama

DAIly outfits: qué es y cuánto cuesta

get_product_info
Read-only

What DAIly outfits is (AI outfit planner / digital closet app), who it's for, price (free, with optional Premium), platforms and download link.

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

Input Schema

NameRequiredDescriptionDefault
langNoIdioma de la respuesta / response language (default es)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds a useful inventory of returned content, which partially compensates for the absent output schema, but says nothing about whether the data is static or fetched live, nor about freshness or source. No contradiction with the annotations.

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?

A single sentence with no padding, and the resource (DAIly outfits) is front-loaded. It reads more like a marketing blurb than a tool definition, which slightly weakens its utility as guidance, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does the minimum by listing the fields the agent will get back (price, platforms, download link). It omits whether the content is static or externally sourced despite openWorldHint, and does not address the language parameter at all, so an agent cannot fully predict the response.

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 description coverage is 100% and the single lang parameter has a self-documenting enum with a default, so the schema carries the semantics. The description never mentions language selection, but with full coverage this is a baseline-3 case rather than a gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates the content the tool surfaces (what the app is, audience, price, platforms, download link), so an agent can infer it returns static product/marketing information about 'DAIly outfits'. However, it is written as a topic list rather than a verb+resource statement, and it never names the app in relation to the tool name get_product_info, leaving the agent to connect them. It implicitly differs from the siblings (packing list, outfit recommendation) but does not say so.

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?

There is no guidance on when to call this versus travel_packing_list or what_to_wear_today, and no statement of when it is inappropriate. The only usable signal is the topic itself, so routing must be inferred entirely from the sibling names.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources