Skip to main content
Glama

wintraits_evidencia

How much evidence is behind it? (¿Cuánta evidencia hay detrás?) Counters: validated findings, launches analysed and used for checking, replication rate, model accuracy versus the baseline, categories, countries and weight of each attribute family in the model.

Args: lang: "es" (default) or "en".

Free and unlimited during the beta (until 2027-01-31). Gratis y sin límite durante la beta (hasta el 31-ene-2027).

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

Input Schema

NameRequiredDescriptionDefault
langNoes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does add real value on one axis — it states the tool is free and unlimited during the beta through 2027-01-31, which is genuine rate/cost information — but says nothing about whether it is read-only, whether it requires credentials, latency, or response format beyond a bare list of counter names.

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 counter list is dense and useful, but the lead sentence is a rhetorical question that occupies prime real estate without informing, and the entire free/beta sentence is duplicated verbatim in Spanish, roughly doubling length for a marginal gain.

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 must explain return values, and the counter enumeration does that at a high level, though 'weight of each attribute family' and 'launches analysed' remain ambiguous. With no annotations and only one parameter, the gaps are mostly around safety and read/write semantics rather than inputs.

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 0% for the single `lang` parameter, and the description compensates well by naming the accepted values ("es" default or "en"), which the schema does not convey beyond a type and default. This is the strongest part of the definition.

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 opens with a rhetorical question ("How much evidence is behind it?") rather than a verb+resource statement, so the actual purpose must be inferred from the enumerated counters (validated findings, replication rate, model accuracy vs baseline, attribute-family weights). Those counters do reveal that it returns model-evidence/methodology statistics, but the definition never plainly says 'returns evidence and accuracy metrics for the model', and it gives no contrast with siblings such as wintraits_hallazgos or wintraits_indice_categoria.

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 tool, when not to, or which sibling to use instead when the agent wants findings versus raw categories versus methodology stats. Usage is left entirely implicit from the counter 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