Skip to main content
Glama

Innovative Workspace

Ask about IW

ask
Read-onlyIdempotent

Ask anything about Innovative Workspace in plain language. Returns the published passages that match (services, prices, FAQs, team, case studies, the company and its pages), word for word with their URLs, and says plainly when the snapshot doesn’t cover the question. It finds text; it doesn’t write answers. Snapshot of https://www.innovativework.space/ taken on 2026-11-20.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "question": "<question>"
    },
    "name": "ask"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many results to return (1 to 10; default 5).
questionYesThe question, in plain language.

Output Schema

NameRequiredDescriptionDefault
noteYes
foundYes
contactYes
resultsYes
snapshotYesThe public site this answer comes from, and when this server took its snapshot of it.
unmatchedTermsYes

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?

With annotations already covering read-only, closed-world, idempotent, and non-destructive behavior, the description adds meaningful traits: verbatim passages with URLs, no generated answers, and an explicit coverage caveat with snapshot date. It does not discuss ranking, pagination, or rate limits, but those are secondary for this retrieval tool.

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?

Three tightly constructed sentences front-load the purpose and return behavior, then add the non-answer caveat and snapshot provenance. Every clause carries useful information with no filler.

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?

For a two-parameter retrieval tool with an output schema and rich annotations, the description supplies the essential context: what content is searched, what is returned, and when coverage is absent. The snapshot URL and date further bound expectations, leaving no material gap for correct invocation.

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 schema already documents the plain-language question and 1–10 limit with defaults. The description echoes 'in plain language' but adds no new syntax or constraints beyond the schema, so 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?

States a specific action (ask in plain language about Innovative Workspace), the retrieval resource (published passages across services, prices, FAQs, team, case studies, company pages), and explicitly distinguishes itself from answer-writing. The breadth across categories implicitly separates it from the single-purpose sibling search and get tools.

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?

Gives clear usage context: plain-language questions about Innovative Workspace, and notes it returns matching passages rather than synthesized answers. It does not name specialized siblings or state when to prefer them, so it falls short of explicit when/when-not/alternatives guidance.

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