Skip to main content
Glama

Detalhes de um listing ou find

designeer_get

Fetch Designeer page or find details from a URL, path, or slug to access palette hex colors, pricing, creator info, media types, and related items.

Instructions

Detalhes de uma página do Designeer: site oficial, categoria, preço, PALETA DE CORES extraída (hex), data, relacionados; em finds: criador, @handle, post original, tipos (Motion, Interface, 3D...). Aceita URL completa, path ('tools/cursor') ou slug de find.

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": {
      "target": "<target>"
    },
    "name": "designeer_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYesURL do Designeer, path tipo 'resources/fontshare' ou slug de find

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 burden. It does partially discharge that by disclosing the returned field inventory and the accepted input forms, which tells the agent this is a read/lookup operation. It is silent on permissions, error behavior when a slug is invalid, rate limits, and whether the color-palette extraction is computed or stored.

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 the return-value inventory and ending with the input forms, with no filler. The semicolon-separated field lists are dense but each item is informative rather than padding.

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?

There is no output schema and no annotations, so the description must describe the return payload — and it does so field by field for both listings and finds. Enough is present for an agent to call and interpret it; only failure modes and auth requirements are unstated.

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% and the single 'target' parameter already documents URL, path, and find slug, so this is largely a restatement rather than new meaning. However, the description reinforces the three accepted forms with a concrete example ('tools/cursor'), which reduces the chance of an agent passing a bare slug to the listing branch.

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 names the resource (a Designeer page) and enumerates what it retrieves, split into two clear modes: listings (site, category, price, extracted hex color palette, date, related) and finds (creator, @handle, original post, types). It does not name a sibling such as designeer_search or designeer_finds to mark the boundary, so an agent must infer that this is the single-item lookup versus the collection tools.

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 rather than stated: pass a full URL, a path like 'tools/cursor', or a find slug and get back details. There is no explicit 'use this when…' clause, no precondition (e.g., that you must first resolve a slug via search), and no when-not guidance against the sibling browse/finds tools.

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