Skip to main content
Glama
Sign In
@opensvg/mcp

@opensvg/mcp

by mahbubhasanhira
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_collections

List open-source icon collections indexed in OpenSVG with icon counts, licenses, and authors so users can compare and choose sets.

Instructions

List popular open-source icon sets indexed in OpenSVG, including total icon count, license, and author.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_collections"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. 'List' implies a read-only operation and the description usefully discloses returned fields, but it says nothing about what 'popular' means (ranking? fixed order?), whether results are paginated or truncated, or how many sets are returned.

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 front-loaded sentence with the resource stated first and the returned fields following. No filler or redundant restatement of the tool name.

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?

For a zero-parameter read tool with no output schema, the description covers enough: what is listed and which fields come back. The main gap is the undefined 'popular' ordering and any result-size limits, which an agent would need to interpret the response correctly.

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?

The tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. The description correctly signals a no-argument listing operation.

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?

States a specific verb (List) and a specific resource (popular open-source icon sets indexed in OpenSVG), and even lists the returned fields (icon count, license, author). It implicitly contrasts with the sibling get_my_collections by scoping to sets 'indexed in OpenSVG' rather than the user's own, though it never names the sibling explicitly.

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?

No when-to-use or when-not-to-use guidance appears. The phrase 'popular open-source icon sets' vaguely suggests discovery/browsing, but nothing tells the agent how this differs from search_icons or get_my_collections, and no prerequisites or exclusions are given.

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

Deploy Server

Other Tools