Skip to main content
Glama

Innovative Workspace

Get an IW service

get_service
Read-onlyIdempotent

One service or programme of Innovative Workspace, word for word from the site: what it is, its page, its published price or that it is quoted, and the FAQs on its 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_service"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
faqsYes
nameYes
titleNo
sourceYes
pricingYes
snapshotYesThe public site this answer comes from, and when this server took its snapshot of it.
descriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/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 safety is covered. The description adds genuinely useful context beyond them: content is verbatim from the site, prices may be 'quoted' rather than published, and there is a dated snapshot (2026-11-20) signalling data freshness. It does not discuss error behavior for an invalid id.

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?

One dense sentence covering content and price/FAQ behavior, followed by a short snapshot-date clause. Front-loaded with the resource, no filler, though the phrase 'word for word from the site' is slightly awkward.

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?

Output schema exists, so return shape needn't be described, and the description still covers content scope, price semantics and snapshot provenance. Only missing piece is guidance on how to obtain a valid id.

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 the five valid values with a description pointing at the search tool, so the schema does the work. The description adds nothing about the id beyond what the schema already states.

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 specific resource (a single Innovative Workspace service/programme) and enumerates what the record contains: description, page, price or quote status, and page FAQs. The singular framing distinguishes it from a list/search tool, though it never names a sibling explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: 'One service' suggests fetching a known item, presumably identified via the search tool, but the description gives no explicit when-to-use rule, no alternative named, and no exclusion such as preferring search_services when the id is unknown.

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