Logo MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract_logoC | 从指定网站URL提取Logo图标链接 |
| analyze_logo_candidatesC | 分析网站的所有Logo候选项并返回详细信息 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one analyzes logo candidates on a website, while the other extracts a logo icon link from a URL. There is no overlap or ambiguity between them, making it easy for an agent to select the correct tool based on the task.
Both tools follow a consistent verb_noun pattern (analyze_logo_candidates and extract_logo), using snake_case throughout. The naming is predictable and readable, with no deviations or mixed conventions.
With only two tools, the server feels thin for a logo-related domain. While the tools cover analysis and extraction, there are likely gaps in functionality (e.g., no tools for creating, updating, or deleting logos), making the scope appear incomplete and potentially limiting for agents.
The tool surface is severely incomplete for a logo management domain. It lacks basic CRUD operations (e.g., create_logo, update_logo, delete_logo) and other expected functionalities like logo validation or comparison. Agents will encounter dead ends when trying to perform common logo-related tasks.