Skip to main content
Glama

The Very Lab

How to send an inquiry

how_to_inquire
Read-onlyIdempotent

How a brand can contact The Very Lab about manufacturing, what to include, and the rules an AI agent must follow. This server cannot send inquiries.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds substantive context beyond that: it explicitly rules out any send-side effect and enumerates the content delivered (contact method, what to include, agent rules). It does not describe the shape of the returned text, which keeps it from a 5.

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?

Two short sentences, front-loaded with the purpose and closed with the most decision-relevant constraint. Every clause earns its place: subject, contents, and the non-action guarantee.

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 informational tool whose annotations already cover safety and side effects, the description says what it delivers and what it will not do. The only residual gap is whether the guidance is returned as static text or requires chaining to another tool, which an agent might want to know.

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 nothing for the description to disambiguate; the baseline for no-parameter tools applies. Nothing in the description misleads about inputs, and the empty schema is consistent with the stated purpose.

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 states the resource precisely: guidance on how a brand contacts The Very Lab about manufacturing. It is clear this is an informational lookup rather than an action. It stops short of a crisp verb ('returns guidance on...') but the subject matter is unambiguous and distinct from siblings like get_company_profile or list_capabilities.

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

Usage Guidelines4/5

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

Includes a strong when-not clause: 'This server cannot send inquiries,' which prevents an agent from attempting to transmit anything through this tool. It does not name an alternative tool for sending, nor does it say when to consult this versus the company profile, so guidance is clear but not fully comparative.

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