Skip to main content
Glama

Vigil Website MCP

list_products

Read-onlyIdempotent

Everything an agent can buy from Vigil, with Stripe-verified prices, billing terms, delivery and live availability.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuinely new context beyond them: prices are Stripe-verified, and results include billing terms, delivery, and live availability. It stops short of saying whether results are paginated or how 'live availability' is refreshed.

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

Conciseness4/5

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

A single dense clause with zero filler, and the resource identity is front-loaded. It reads as a noun phrase rather than a sentence, which makes the action slightly less explicit than it could be, but nothing is wasted.

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?

With no output schema, the description carries the burden of describing the return payload, and it does so by naming prices, billing terms, delivery, and availability. For a zero-parameter catalog read this is close to sufficient, though it omits result shape or completeness guarantees.

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, so the baseline is 4 and there is no parameter ambiguity to resolve. Nothing in the description misdescribes the input surface.

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?

The description conveys a catalog-listing operation ('Everything an agent can buy from Vigil'), which is a specific resource and clearly distinct from the transactional siblings create_checkout and get_checkout. It never uses the verb 'list' or says it enumerates products, so the verb is inferred from the name rather than the text.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the browse step that precedes create_checkout, but the description never says when to call it or points at any alternative. There are no prerequisites, exclusions, or routing hints, leaving the agent to guess the workflow position.

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.

Resources