Skip to main content
Glama

The Very Lab

Manufacturing capabilities

list_capabilities
Read-onlyIdempotent

What The Very Lab manufactures: product categories, service models (white label, private label, contract manufacturing), minimum order quantity, who it is and is not a fit for, and where to read more.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description adds the substantive scope of the returned content, which is useful context, but says nothing about format, size, or freshness of the capability data.

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 front-loaded sentence that leads with the subject ('What The Very Lab manufactures') and then enumerates the returned sections. The parenthetical service models are informative rather than filler; only the trailing 'where to read more' is slightly vague.

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 zero parameters, no output schema, and full annotation coverage, the only burden on the description is telling the agent what content comes back, and it does that thoroughly. The remaining gap is minor: it doesn't indicate whether the response is structured fields or prose, which would help an agent decide how to consume it.

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 there is no parameter semantics to explain and the baseline of 4 applies. The description correctly does not invent inputs, confirming this is an unfiltered capability listing.

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 enumerates the exact content the tool returns: product categories, service models (white label, private label, contract manufacturing), MOQ, fit criteria, and further reading. That is a specific resource scope rather than a tautology of the name. It doesn't explicitly say 'retrieve/list' as a verb, which keeps it just short of 5.

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?

The content list implies when an agent would call it (questions about what the company makes, service models, or order minimums), and 'who it is and is not a fit for' hints at qualification questions. However, there is no explicit when-to-use or when-not, and no reference to the nearby siblings like get_company_profile or how_to_inquire.

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