Skip to main content
Glama

Sized favicon links

bpj_responsive_favicon_links
Read-onlyIdempotent

Validate square pixel sizes or any and build icon links carrying sizes attributes.

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": {
      "icons": "<icons>"
    },
    "name": "bpj_responsive_favicon_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only that it validates sizes and builds link markup; it does not explain error behavior, output shape, or what 'any' means in practice.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no filler, so it is concise. However, it is syntactically awkward and front-loads an unclear phrase, reducing clarity.

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

Completeness2/5

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

For a one-parameter utility, the description leaves the required input format and the generated output unstated. With no output schema and 0% parameter coverage, it should explain how to supply size/URL and what link markup results.

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?

The sole required parameter has 0% schema description coverage, so the description must carry the burden. It hints that the input relates to square pixel sizes or 'any' and an icon URL, but does not define the string syntax, allowed values, delimiters, or how size and URL are combined.

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

Purpose3/5

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

The description names actions (validate sizes, build icon links) and a resource (favicon links), so the general purpose is inferable. However, the phrasing 'Validate square pixel sizes or any and build icon links carrying sizes attributes' is garbled and the 'or any' clause obscures scope.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool instead of sibling link or icon tools, and no preconditions or exclusions are stated. The only implied usage cue is the vague 'square pixel sizes or any' input option.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.