Skip to main content
Glama
Sign In

Refy

by design.refy
OverviewDiscussionsAdmin

Buscar componente por intenção

refy_search
Read-onlyIdempotent

Encontra a família do Refy para uma necessidade descrita em português, inglês ou espanhol ("confirmar antes de apagar", "lista suspensa com busca"). Devolve as famílias em ordem, com o motivo, como usar, quando usar outra e o import.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "refy_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesA necessidade da tela, em linguagem natural.
versionNoVersão do pacote cuja API você quer ler (ex.: 1.2.0). Padrão: a versão deste servidor.
collectionNoFiltra por coleção (core, media, geolocation, conversation, analytics...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds real value beyond that by disclosing the return shape (ordered families with reason, usage, when to use another, and the import) and the multilingual query support — helpful given there is no output schema.

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?

Two sentences, front-loaded with purpose, then inline examples, then the return contents. No filler; every clause carries information. Minor spacing only, no wasted wording.

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?

With no output schema, the description usefully explains what comes back (ordered families with reason, usage hints, import). It covers the core search intent well; the remaining gaps (limit default/behavior, collection filtering) are minor because those params are largely documented in the schema.

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 75%, so query, version and collection are documented in the schema already. The description adds meaning to 'query' (natural-language need in pt/en/es with examples), but says nothing about 'limit' (the one undocumented param) or how 'collection' filters. Baseline 3 is appropriate.

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+resource ("Encontra a família do Refy") scoped to a natural-language need, and the examples ('confirmar antes de apagar', 'lista suspensa com busca') make the 'search by intent' angle concrete versus a plain component lookup. It does not explicitly name how it differs from siblings like refy_component or refy_collections, which keeps it just short of a 5.

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

Usage Guidelines3/5

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

Usage is implied: use it when you have a screen requirement phrased in natural language, and it accepts pt/en/es. But there is no explicit when-not-to-use guidance and no named alternative to route to (e.g. use refy_component for a known family). The phrase 'quando usar outra' refers to the returned content, not to choosing a sibling tool.

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

All Refy toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources