Skip to main content
Glama

Innovative Workspace

Get an IW team member

get_expert
Read-onlyIdempotent

One member of Innovative Workspace's team: name and title as on the site, bio, LinkedIn and their place on the About page. 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": {
      "id": "<id>"
    },
    "name": "get_expert"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe team member's id, as the search tool returns it.

Output Schema

NameRequiredDescriptionDefault
idYes
bioNo
urlYes
nameYes
sourcesYes
jobTitleYes
linkedinNo
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

A3.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, so the description only needs to add context. It does: it discloses that the data is a static snapshot of the site taken on 2026-11-20, telling the agent results are point-in-time and may be stale.

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?

Two compact sentences with no filler: fields first, provenance second. The first sentence is elliptical ('One member...') but every clause carries information, and nothing is redundant.

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?

An output schema exists, so return-value enumeration is a bonus rather than a requirement, and the annotations fully cover the safety profile. The one real gap is navigation guidance for obtaining a valid id, which is only partially handled via the schema's reference to the search tool.

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 single id parameter carries an enum of three valid values plus a description pointing to the search tool, so the schema already does the semantic work. The description adds no extra meaning about the id beyond what is structured.

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?

States a concrete verb-ish resource: 'One member of Innovative Workspace's team' and enumerates the returned fields (name, title, bio, LinkedIn, About-page placement). The word 'One' implicitly contrasts with the search_experts sibling, but the description never names that alternative, so differentiation is inferential rather than explicit.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not guidance and no mention of search_experts as the way to discover valid ids. The only hint that this is a lookup-by-id tool comes from the schema, not the description.

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