Skip to main content
Glama
Sign In

Emblematic

by dev.emblematic
OverviewDiscussionsAdmin

What a site uses

get_site
Read-onlyIdempotent

Use this to answer "what font/colors/framework does use?" for one site. Returns brand name, fonts with roles and weights, role colors, hues, detected stack (framework, CMS, hosting) and capture date. If the site is not indexed it says so (found: false) with the closest indexed sites. Not for building UI from the spec (use get_design).

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": {
      "site": "<site>"
    },
    "name": "get_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesIndexed site as a slug ("linear.app"), URL ("https://linear.app/pricing") or brand name ("Linear").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety needs no restating. The description adds genuine behavior beyond that: the not-indexed case returns found: false plus the closest indexed sites, which an agent otherwise could not anticipate. It stops short of describing shape or size of the stack payload, keeping it a 4 rather than a 5.

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 sentences, front-loaded with the triggering question, then the return payload, then the failure mode, then the exclusion. No filler and no repetition of the title.

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

Completeness5/5

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

There is no output schema, so the description carries the return contract, and it does: it lists the fields returned, declares the fallback behavior when a site is not indexed, and routes UI-building work elsewhere. Nothing an agent needs in order to call this correctly is missing.

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 100% and the single parameter already documents slug, URL, and brand-name forms with an example. The description only says 'for one site', adding essentially nothing about accepted input formats beyond what the schema provides, so the baseline 3 applies.

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

Purpose5/5

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

The description gives a specific verb-plus-resource framing ('answer what font/colors/framework does <site> use for one site') and enumerates what is returned: brand name, fonts with roles and weights, role colors, hues, detected stack, and capture date. It explicitly separates itself from get_design, so an agent can pick it without opening any schema.

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

Usage Guidelines5/5

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

It states the exact question this tool answers, scopes it to a single site, and gives an explicit exclusion with the alternative: 'Not for building UI from the spec (use get_design).' That is when-to-use, when-not-to-use, and the named substitute in one place.

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

All Emblematic 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