Skip to main content
Glama

Innovative Workspace

Search IW FAQs

search_faqs
Read-onlyIdempotent

Search the frequently asked questions published on Innovative Workspace's site, with their answers word for word and the page each is on. Leave the query out to list them. Snapshot of https://www.innovativework.space/ taken on 2026-11-20.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many results to return (1 to 30; default 10).
queryNoWords to look for, in plain language. Leave it out to list everything.

Output Schema

NameRequiredDescriptionDefault
noteNo
totalYes
resultsYes
snapshotYesThe public site this answer comes from, and when this server took its snapshot of it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. Beyond that, the description adds two genuinely useful behavioral facts: results are verbatim answers with their source page, and the corpus is a snapshot of https://www.innovativework.space/ taken on 2026-11-20, which warns the agent that content may be stale. It does not discuss result volume or truncation behavior, but the schema already caps that.

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 sentences, both front-loaded with the most decision-relevant information (what is searched, what comes back, how to list instead, and the snapshot caveat). No filler, no repetition of the title, and the listing shortcut is stated immediately after the core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present the description need not describe return structure, and the annotations carry the safety and idempotency profile. Given only two optional, fully documented parameters, the description covers purpose, the browse-vs-search switch, and data provenance -- everything an agent needs to call it correctly.

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 description coverage is 100% -- both 'limit' (1 to 30, default 10) and 'query' (plain-language words, max 200 chars) are documented in the schema itself. The description's only parameter-relevant statement, that leaving the query out lists everything, restates the schema rather than adding syntax, matching behavior, or format guidance, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (Search) and a specific resource (the FAQs published on Innovative Workspace's site), and it goes further by stating exactly what each result contains: the answer verbatim plus the page it appears on. That resource name is self-evidently distinct from the sibling tools (case studies, experts, services, pricing), so an agent can route correctly without opening a schema.

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 one concrete usage rule -- omit the query to list everything -- which tells the agent how to switch from searching to browsing. What it lacks is any routing guidance against alternatives (e.g., when to prefer search_faqs over ask for a question that might be answered by an FAQ), so the agent must infer that boundary itself.

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