Skip to main content
Glama

Últimos finds

designeer_finds

Search and browse recently curated visual design references from X and the web, credited to creators, to source motion, interface, 3D, typography, and branding inspiration.

Instructions

Finds = trabalhos visuais recentes (motion, interface, 3D, tipografia, branding) garimpados do X e da web, creditados ao autor. Ótimo pra referência de motion/microinteração. Use designeer_get pra criador/paleta e designeer_media pra ver o vídeo.

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

Input Schema

NameRequiredDescriptionDefault
queryNoFiltra pela descrição/autor (local, na página atual)
cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses provenance (X and web), recency, authorship credit, and content categories, but it does not state read-only behavior, pagination, result format, freshness, or filtering scope. This provides meaningful context but leaves important operational behavior undocumented.

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?

Three short sentences are front-loaded with the definition, followed by the recommended use case and precise sibling routing. Every sentence earns its place, with no repetition or filler.

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?

For a simple two-parameter discovery tool, the description explains what finds are, where they come from, and which siblings to use for adjacent needs. However, with no output schema and no annotations, it should disclose at least cursor/pagination behavior and what the response contains. It is adequate for selection but incomplete for confident invocation.

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

Parameters2/5

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

Schema description coverage is only 50%: query is documented as filtering by description/author locally on the current page, while cursor has no schema description. The tool description says nothing about either parameter, so it adds no meaning beyond the schema and fails to compensate for the undocumented cursor.

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?

The description defines the resource concretely as recent visual works in motion, interface, 3D, typography, and branding sourced from X and the web. It is distinguishable from designeer_get and designeer_media by naming their different purposes. The only slight gap is that it does not explicitly state the operation as a list or search, though 'Finds =' implies retrieval.

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?

It gives clear when-to-use guidance: 'Ótimo pra referência de motion/microinteração.' It also routes adjacent needs to designeer_get for creator/palette and designeer_media for video. It does not explain when to prefer this over other discovery siblings such as designeer_search or designeer_browse, so it falls short of a fully explicit alternatives matrix.

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