Skip to main content
Glama

COVER

COVER FAQ

cover_search_faq
Read-onlyIdempotent

Searches the frequently asked questions on the COVER product page. Leave query empty to list every question.

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

Input Schema

NameRequiredDescriptionDefault
queryNoWords to look for, e.g. "MISRA" or "air-gapped".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare this a safe, idempotent, non-destructive read of a closed domain, so the description's burden is lighter. It adds the empty-query listing behavior, which is genuinely useful, but says nothing about match semantics (substring vs. fuzzy, case sensitivity) or the shape of results.

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 with no filler; the core action comes first and the empty-query edge case follows immediately. Nothing is redundant.

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 simple, read-only, one-optional-parameter search tool with rich annotations and no output schema, this is nearly sufficient. The only meaningful gap is how matching works and what a result entry looks like, which an agent may want before crafting a narrow query.

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?

Schema coverage is 100%, so the single parameter is already documented with an example. The description adds meaning the schema lacks: an empty query is not a no-op but a request to list all questions, which changes how an agent should call it.

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 names a specific verb and resource — searching the frequently asked questions on the COVER product page — which is distinct from all listed siblings (sections, contact, resources, languages). It does not explicitly name or rule out an alternative tool, but no sibling appears to overlap with FAQ search, so 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 Guidelines4/5

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

It gives clear operating context: search with a query, or omit the query to enumerate every question. That covers both modes of use. It stops short of explicit when-not guidance or naming alternatives, but none are plausibly needed here.

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