Skip to main content
Glama

STATIC

STATIC FAQ

static_search_faq
Read-onlyIdempotent

Searches the frequently asked questions on the STATIC 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": "static_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.7/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 covered. The description contributes the empty-query enumeration behavior, which is genuine added context, but says nothing about result shape (snippets vs. full answers), match semantics (substring vs. keyword), or result limits.

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 core action, with the empty-query rule immediately following. Nothing is padded or repeated from the schema.

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 read-only lookup with full annotation coverage and no output schema, the description covers what to search and how to enumerate, which is nearly everything an agent needs. A brief note on what a result contains would close the remaining gap.

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% and the single parameter already has an example, so baseline is 3. The description earns an extra point by documenting the default-mode semantics (empty query = list all questions), which the schema does not state and which meaningfully changes how the agent calls the tool.

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 ('searches') and resource ('frequently asked questions on the STATIC product page'), which is clearly distinct from sibling resources like contact, sections, or supported languages. It stops short of explicitly contrasting itself with any sibling, but the resource naming alone disambiguates well.

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?

It adds one useful usage rule: leaving the query empty lists every question, which tells the agent how to enumerate the FAQ. There is no explicit statement of when to prefer this over other STATIC tools or when the FAQ source is unsuitable, so guidance is implied rather than spelled out.

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