Skip to main content
Glama
Sign In
ToolSnap MCP

ToolSnap MCP

by ToolSnap-app
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Browse tool catalog

tool_catalog
Read-only

Browse 47 available tools by family or exact name to view descriptions, schemas, pricing, and notes, then run selected tools via use_tool.

Instructions

Free, read-only, no network. Browse all 47 tools in 10 families (web, seo, data, documents, images, media, utils, payments, recipes, meta). No args: families with id, label, one-liner, tool count. family='': each tool with name, price, description, notes, inputSchema. tool='': that entry alone; wins over family. Unknown ids error naming the valid families. Run what you find via use_tool.

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": "tool_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolNoExact tool name, e.g. 'fetch_rendered'. Takes precedence over family.
familyNoFamily id, e.g. 'web', 'data'. Lists its tools with schemas.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.5
    • changedInput schema / properties / family / description
      Previous value: -"Family id → its tools."New value: +"Family id, e.g. 'web', 'data'. Lists its tools with schemas."
    • changedInput schema / properties / tool / description
      Previous value: -"Tool name → detail."New value: +"Exact tool name, e.g. 'fetch_rendered'. Takes precedence over family."
  2. Addedv0.1.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, yet the description still adds real context: 'Free', 'no network', the precedence resolution order, and that unknown ids error while naming valid families. It does not, however, discuss whether catalog contents are static or change over time.

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?

Front-loads the safety/scope facts, then walks the three call modes in the order an agent would try them. Telegraphic clauses carry high information density with no filler sentences.

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, and the description compensates by enumerating the returned fields for each of the three modes, plus error behavior and the handoff to use_tool. Nothing needed to call it correctly is missing.

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?

Schema coverage is 100%, so the baseline would be 3, but the description goes further by spelling out what each parameter mode returns (families with id/label/one-liner/count; tools with name/price/description/notes/inputSchema) and by stating the precedence between tool and family.

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?

States a specific verb and resource (browse the tool catalog) plus concrete scope: 47 tools across 10 named families. The final sentence ('Run what you find via use_tool') separates it from the sibling that actually executes tools, so an agent can distinguish the two without opening either 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?

Gives explicit mode selection: no args for the family index, family='<id>' for tools with schemas, tool='<name>' for a single entry, plus the precedence rule 'wins over family'. It also names the alternative tool for execution and states the failure mode for unknown ids.

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