Skip to main content
Glama
Sign In
MCP-Insomnia

MCP-Insomnia

by anggasct
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_insomnia_collections

List all API collections from your local Insomnia app to efficiently manage and organize your API projects.

Instructions

List all collections directly from Insomnia app (requires Insomnia to be installed)

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_insomnia_collections"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.2
  2. Removedv0.3.0
  3. First observedv0.4.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided, so description must disclose behaviors. Only mentions prerequisite (Insomnia installed). Does not describe behavior if Insomnia is missing, rate limits, or response format.

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?

Single sentence with essential information, front-loaded. No wasted words.

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

Completeness3/5

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

Tool is simple with no parameters, but lacks description of return values or output format. Does not differentiate from similar siblings like 'list_collections' sufficiently for agents to choose 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?

No parameters in schema, baseline 4 per instructions. Description does not need to add parameter details, but also does not add any extra insight beyond the empty schema.

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?

Clearly states the tool lists all collections from Insomnia app, specifying verb ('list'), resource ('collections'), and source ('Insomnia app'). Does not explicitly distinguish from sibling 'list_collections', but the phrase 'directly from Insomnia app' hints at differentiation.

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 guidance on when to use this tool vs alternatives like 'list_collections' or 'get_insomnia_collection'. Lacks context for selection among siblings.

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