Skip to main content
Glama

DocuQueue MCP

by io.github.dvcoolarun
OverviewDiscussionsAdmin

extract_branding

Read-onlyIdempotent

Extract colors, fonts, and logo from a website.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
websiteYesWebsite URL to analyze

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
fontNo
websiteYes
logo_urlNo
company_nameNo
primary_colorNo
secondary_colorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / website / description
      Added value: +"Website URL to analyze"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "company_name": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "font": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "logo_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "primary_color": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "secondary_color": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "website": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "website"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds that it fetches from a website (implied network access) but provides no additional behavioral detail like rate limits or response structure. It does not contradict annotations.

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?

A single sentence with no filler. The core action and scope are front-loaded, making it immediately understandable. Nothing unnecessary.

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?

With an output schema present and annotations covering safety, the description is complete for this simple one-parameter tool. It states what is extracted, and the output schema would detail the return format. No critical information 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% – the 'website' parameter is described as 'Website URL to analyze'. The tool description adds no extra meaning beyond that, so the schema carries the full parameter explanation. Baseline of 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 states a specific verb (extract), a resource (website), and the exact items extracted (colors, fonts, logo). This clearly differentiates it from sibling tools focused on template creation, PDF download, or deck generation.

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: you would call this when you need branding assets from a website. However, there is no explicit statement of when to use it versus alternatives, nor any exclusions. The sibling tool names provide context but the description itself lacks direct guidance.

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

All DocuQueue MCP 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