Skip to main content
Glama

Innovative Workspace

Search the IW team

search_experts
Read-onlyIdempotent

Search Innovative Workspace's team (its directors), by name, role or expertise. Leave the query out to list everyone; use get_expert for a bio. 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_experts"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the dataset is a snapshot of the site taken on 2026-11-20 (data freshness) and the scope is limited to directors. It does not mention result limits or pagination, which keeps it from a 5.

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, zero filler. Purpose and searchable fields come first, the optional-query behavior and sibling pointer next, and the data-freshness caveat is placed last as supporting detail rather than leading with it.

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?

Output schema exists, so return values need not be explained. With a single optional parameter, rich annotations, and a snapshot provenance note, an agent has everything needed to call this correctly and to interpret the results' currency.

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 baseline is 3. The description goes beyond the schema by specifying which fields the query matches against (name, role, expertise) — the schema's own parameter text only says "words to look for, in plain language." That added matching semantics is useful for query construction.

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 verb and resource ("Search Innovative Workspace's team (its directors)") and immediately narrows the searchable fields to "name, role or expertise." It also distinguishes itself from the sibling get_expert, so an agent can route between them without opening either schema.

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?

Explicitly covers the boundary case: "Leave the query out to list everyone" tells the agent the parameter is optional and what happens without it. It also names the alternative (get_expert) and the condition that selects it (need a bio). Both when-to-use and when-to-go-elsewhere are stated.

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