Skip to main content
Glama

Innovative Workspace

Search IW services

search_services
Read-onlyIdempotent

Search Innovative Workspace's services and programmes (Your Own AI Starter; AI agents; AI consulting; 3–4 week pilot; AI for nonprofits, from a nonprofit). Leave the query out to list them all. Each result says whether its price is published or quoted; use get_service for the details. 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_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many results to return (1 to 20; 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?

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile needs no restating. The description adds genuinely new behavioral context beyond the annotations: results carry a price-published vs price-quoted flag, and the index is a dated snapshot (2026-11-20), which tells the agent the data may be stale. It stops short of describing ranking or empty-result behavior, but the output schema covers the return shape.

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?

The core scope and the get_service hand-off are front-loaded in the first two sentences, and every sentence carries information. The parenthetical catalogue of example offerings is somewhat long, but it does help the agent match user phrasing to this tool, so it mostly earns its space.

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?

With an output schema present, rich annotations, and fully documented parameters, the description's job is limited, and it covers the extra pieces an agent needs: the snapshot date, the price-flag signal, and the detail-tool hand-off. Only minor gaps remain, such as pagination or zero-match behavior, which the schema largely absorbs.

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%, and both parameters already have documented bounds and defaults. The description's "leave the query out to list them all" largely restates the query parameter's own description, and it adds nothing about the limit parameter or query matching semantics, so the baseline 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 opens with a specific verb and resource ("Search Innovative Workspace's services and programmes") and enumerates the content types it covers, so an agent knows exactly what domain this tool queries. It also distinguishes itself from the sibling get_service by framing itself as the discovery step and get_service as the detail step.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It gives two explicit operating instructions: omit the query to list everything, and call get_service to get the details of a specific result. That is a concrete when-to-use plus a named alternative for the follow-up action, leaving little to inference.

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