Skip to main content
Glama

Velvet FAQ

get_faq
Read-onlyIdempotent

Velvet's published questions and answers, optionally only those containing a word.

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

Input Schema

NameRequiredDescriptionDefault
containsNoOnly questions or answers containing this word, e.g. 'refund'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / contains / description
      Added value: +"Only questions or answers containing this word, e.g. 'refund'."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered elsewhere. The description adds one useful behavioral fact, that only 'published' content is returned, but says nothing about result size, ordering, or what happens when the filter word matches nothing.

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 short clause with no filler, and the core resource is front-loaded before the optional filter. The slightly telegraphic phrasing costs it a perfect score 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?

For a one-parameter, zero-required read tool with rich annotations and no output schema, the definition covers what the tool returns at a high level (published Q&A pairs) and how to narrow it. Only the absence of any hint about result shape or volume keeps it below 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the sole parameter already carries a description plus an example ('refund'), so the schema does the heavy lifting. The description only restates the filter in prose and adds no matching semantics such as case sensitivity or whether it applies to questions, answers, or both.

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?

States a specific resource ('Velvet's published questions and answers') and the optional narrowing condition, which lets an agent distinguish it from sibling resources like about_velvet or get_pricing. It is a noun phrase rather than a verb+resource construction, but the purpose is unambiguous.

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?

The description offers no when-to-use guidance, no exclusions, and does not point at any alternative. The closest thing to guidance is the word 'optionally', which describes the parameter rather than when to choose this tool over a sibling.

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